work-gates

You can enforce must-fix code quality standards by applying project-specific quality gates that reject stubbed code paths and enforce test integrity rules. This skill formalizes governance requirements to maintain pipeline quality and prevent regressions.

Quality gates are project-specific checkpoints that enforce must-fix standards for code health and consistency. You need them when extending a core task-work skill to safeguard maintainability and prevent unsafe code paths from entering your codebase.

Set up test integrity rules and build verification by enabling this skill to automatically apply quality gates during development. It optionally wires in scripts, references, or assets to enhance checks and maintain pipeline quality.

Yes, you can use project-specific quality gates with an existing task-work skill. This skill supplements the core task-work skill by adding project-specific checks, must-fix patterns, and governance guidance without requiring external dependencies.

No, this code quality governance skill requires no external dependencies. It optionally wires in scripts, references, or assets for enhanced checks when present, but operates by formalizing governance requirements directly in the SKILL.md file.

Quality gates go beyond standard lint checks by enforcing must-fix patterns that reject stubbed or unsafe code paths and formalize test integrity rules. They supplement standard linting with project-specific governance requirements to ensure maintainable code.