---

name: quality-gateway description: > Orchestrates quality checks at key lifecycle points: before edits, after edits, and before completion. Coordinates sub-skills (test-augmentation, doc-sync, coding-standards, security-review) to ensure consistent code quality. Use when making significant code changes or before completing a task. compatibility: Requires Node.js 24+; works with any codebase metadata: version: "1.0"

Quality Gateway

Orchestrates quality checks at key lifecycle points in the development workflow. This skill coordinates sub-skills to ensure consistent code quality.

When to Use This Skill

• Before starting significant code changes (pre-edit baseline)
• After completing code changes (post-edit validation)
• Before marking a task as complete (final quality gate)
• When running the /quality-check command

Skill Contents

Sections

• When to Use This Skill (L16-L22)
• Sub-Skills (L49-L59)
• Lifecycle Hooks (L60-L67)
• IDE Integration (L68-L78)
• Quality Checks (L79-L101)
• Commands (L102-L109)
• Assets (L110-L116)
• References (L117-L122)
• Test Result Caching (L123-L137)
• Related Skills (L138-L144)

Available Resources

📚 references/ - Detailed documentation

• test result caching

📦 assets/ - Templates and resources

• claude quality hooks
• cursor quality integration

---

Sub-Skills

The quality gateway orchestrates these sub-skills:

Lifecycle Hooks

IDE Integration

The quality gateway integrates with AI IDEs through hooks:

For hook implementation patterns, see the agent-hooks skill in .claude/skills/agent-hooks/.

Quality Checks

Pre-Edit (Baseline)

Before making changes:

1. Record current test coverage
2. Note existing linting errors
3. Capture documentation state

Post-Edit (Validation)

After making changes:

1. Verify test coverage maintained or improved
2. Check for new linting errors
3. Validate documentation is in sync

On-Stop (Final Gate)

Before completing:

1. Run full test suite
2. Verify no regressions
3. Check all quality thresholds met

Commands

Assets

References

Test Result Caching

Always save test output to .tmp/ instead of running tests multiple times:

Copy# Run once and save
pnpm test 2>&1 | tee .tmp/pnpm-test-latest.txt

# Then grep from file (don't run tests again!)
grep "FAIL" .tmp/pnpm-test-latest.txt
tail -20 .tmp/pnpm-test-latest.txt

See references/test-result-caching.md for all tools.

Related Skills

• agent-hooks - Hook implementation patterns (in targeted/skills/)
• test-augmentation - Test coverage validation
• doc-sync - Documentation synchronization
• coding-standards - Code style enforcement
• security-review - Security vulnerability checks