Quality Gateway

Run comprehensive quality gate checks on code changes. Orchestrates quality checks at key lifecycle points in the development workflow.

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 asked to run "quality check" or "quality gate"

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

Sub-Skills

The quality gateway orchestrates these sub-skills:

| Sub-Skill | Purpose | Skill Location | |-----------|---------|----------------| | test-augmentation | Validates test coverage | .claude/skills/test-augmentation/ | | doc-sync | Validates documentation | .claude/skills/doc-sync/ | | coding-standards | Enforces code style | .claude/skills/coding-standards/ | | security-review | Checks for vulnerabilities | .claude/skills/security-review/ |

Lifecycle Hooks

| Hook | When | Purpose | |------|------|---------| | pre-edit | Before changes | Capture baseline metrics | | post-edit | After changes | Validate changes meet standards | | on-stop | Before completion | Final quality gate |

IDE Integration

The quality gateway integrates with AI IDEs through hooks:

| IDE | Integration Method | Reference | |-----|-------------------|-----------| | Claude Code | Native hooks in settings.json | assets/claude-quality-hooks.md | | Cursor IDE | Rules + Commands | assets/cursor-quality-integration.md |

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

Quality Checks

Pre-Edit (Baseline)

Before making changes:

Record current test coverage
Note existing linting errors
Capture documentation state

Post-Edit (Validation)

After making changes:

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

On-Stop (Final Gate)

Before completing:

Run full test suite
Verify no regressions
Check all quality thresholds met

Commands

| Command | Purpose | |---------|---------| | /quality-check | Run full quality gate | | /add-tests | Generate missing tests | | /sync-docs | Update documentation |

Assets

| Asset | Description | |-------|-------------| | assets/claude-quality-hooks.md | Claude Code hook configurations | | assets/cursor-quality-integration.md | Cursor IDE integration guide |

References

| Reference | Description | |-----------|-------------| | references/test-result-caching.md | How to save and reuse test results |

Test Result Caching

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

# 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