quality-gate-calculator

Calculate quality gate thresholds by work type and development phase.

1|1|Updated Jun 28, 2025
One-click install
npx skills add https://github.com/DarkMonkDev/WitchCityRope --skill quality-gate-calculator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-gate-calculator
Source: https://github.com/DarkMonkDev/WitchCityRope/tree/main/.claude/skills/quality-gate-calculator
Command: npx skills add https://github.com/DarkMonkDev/WitchCityRope --skill quality-gate-calculator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, and includes scripts (resource) components.

What problem does it solve?

Applying a one-size-fits-all quality standard to diverse work types (features, bugs, hotfixes) leads to either over-engineering simple tasks or compromising quality on critical ones. This Skill ensures appropriate rigor.

Core Features & Use Cases

  • Contextual Thresholds: Calculates quality gate percentages and score targets based on work type (Feature, Bug, Hotfix, Documentation, Refactoring) and development phase.
  • Universal Test Pass: Enforces a non-negotiable 100% test pass rate for all work types in the Testing Phase (Phase 4).
  • Rationale Provided: Explains the reasoning behind each quality gate, balancing quality with velocity.
  • Use Case: At the start of a new bug fix workflow, use this Skill to instantly determine the exact quality score needed for each phase, from requirements to finalization.

Quick Start

Calculate the quality gate for a 'Bug' fix in 'Phase 3'.

Frequently Asked Questions about quality-gate-calculator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set quality gates for different work types in my development workflow?

Quality gates adapt to work type and phase. This Skill calculates context-appropriate thresholds for Feature, Bug, Hotfix, Documentation, and Refactoring across five phases—Requirements through Finalization—so each work type gets proportional rigor without over-engineering simple tasks or compromising critical ones.

What quality standards should a bug fix meet at each development phase?

Bug fixes require phase-specific quality percentages: Requirements and Design phases have lower thresholds to move quickly, Implementation raises standards, Testing enforces 100% test pass rate, and Finalization ensures stability. Exact percentages depend on the phase and are provided via CLI output.

Can I enforce consistent test pass rates across all work types?

Yes. Across Features, Bugs, Hotfixes, Documentation, and Refactoring, this Skill enforces a universal 100% test pass rate requirement in the Testing phase to maintain non-negotiable quality while allowing flexibility in earlier phases.

How do I determine the right quality score target for my current work phase?

Run the CLI with your work type and phase as inputs. The Skill outputs the required percentage and target score, exports configuration to /tmp/quality-gate.env, and provides rationale and pass/fail examples tailored to your context.

What's the difference between quality gates for features versus hotfixes?

Hotfixes typically require higher thresholds than features in early phases due to production risk, while features can iterate more freely. This Skill calculates work-type-specific gates to balance velocity with appropriate rigor for each scenario.

Can I use this Skill in automated CI/CD workflows?

Yes. The Skill provides a CLI interface via execute.sh that outputs results to /tmp/quality-gate.env, making it suitable for shell-based automation and integration into build pipelines and continuous delivery systems.