Skip to content
quality-gateway logo

Quality Gateway

quality-gateway

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.

NeverSight/skills_feed0installs213stars

SKILL.md

Full skill instructions

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

Available Resources

📚 references/​ - Detailed documentation

📦 assets/​ - Templates and resources


Sub-Skills

The quality gateway orchestrates these sub-skills:

Sub-SkillPurposeSkill Location
test-augmentationValidates test coverage.claude/​skills/​test-augmentation/
doc-syncValidates documentation.claude/​skills/​doc-sync/
coding-standardsEnforces code style.claude/​skills/​coding-standards/
security-reviewChecks for vulnerabilities.claude/​skills/​security-review/

Lifecycle Hooks

HookWhenPurpose
pre-editBefore changesCapture baseline metrics
post-editAfter changesValidate changes meet standards
on-stopBefore completionFinal quality gate

IDE Integration

The quality gateway integrates with AI IDEs through hooks:

IDEIntegration MethodReference
Claude CodeNative hooks in settings.jsonassets/​claude-quality-hooks.md
Cursor IDERules + Commandsassets/​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:

  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

CommandPurpose
/​quality-checkRun full quality gate
/​add-testsGenerate missing tests
/​sync-docsUpdate documentation

Assets

AssetDescription
assets/​claude-quality-hooks.mdClaude Code hook configurations
assets/​cursor-quality-integration.mdCursor IDE integration guide

References

ReferenceDescription
references/​test-result-caching.mdHow 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
<!-- AUTO-GENERATED FILE - DO NOT EDIT DIRECTLY --> <!-- Source: bitsoex/​ai-code-instructions → global/​skills/​quality-gateway/​SKILL.md --> <!-- To modify, edit the source file and run the distribution workflow -->