quality-gate-review
Quality Gate Review applies pass/fail criteria at each development stage—from idea to release—ensuring standards compliance and generating audit trails. It defines checklists for gate transitions, verifies acceptance criteria with evidence, and tracks quality metrics including code complexity and defect rates.
Quality Gate Review enforces quality gates and verifies compliance with standards across development stages.
AI-generated summary based on this skill's SKILL.md
Install
duc01226/EasyPlatform/quality-gate-review · repository language: C#
git clone https://github.com/duc01226/EasyPlatform
cp -r EasyPlatform/.agents/skills/quality-gate-review ~/.claude/skills/quality-gate-reviewnpx skillfed install duc01226/EasyPlatform/quality-gate-reviewFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What is quality gate review process and how does it work?
Quality Gate Review applies pass/fail criteria at each development stage—from idea to release—ensuring standards compliance and generating audit trails. It defines checklists for gate transitions, verifies acceptance criteria with evidence, and tracks quality metrics including code complexity and defect rates to enforce quality gates across development.
How does Quality Gate Review enforce compliance verification?
Quality Gate Review enforces compliance by establishing stage-specific checklists and verification criteria. It requires evidence of acceptance criteria met before advancement, tracks metrics like cyclomatic complexity and mutation scores against thresholds, and maintains audit trails documenting each gate decision and the standards applied.
What quality metrics tracking and audit trail does it generate?
Quality Gate Review generates comprehensive audit trails tracking quality metrics throughout the development lifecycle. It captures defect escape rates, first-time-right percentages, code quality measurements, and gate pass/fail decisions with timestamps and evidence. This creates a complete record for process improvement and compliance verification.
How does Quality Gate Review handle PO sign-off for releases?
Quality Gate Review includes a release readiness gate where acceptance criteria are verified and documented for PO sign-off. The skill ensures all pre-release quality checklists pass, code review standards are met, and quality metrics meet thresholds before feature release approval is obtained from the product owner.
What pre-release checklist items does Quality Gate Review verify?
Quality Gate Review's pre-release checklist verifies code quality standards, cyclomatic complexity thresholds, mutation scores, acceptance criteria completion, and defect metrics. It confirms dev-to-QA gate passage, validates artifact tracking, and ensures all development lifecycle quality control steps are complete before deployment authorization.
How does Quality Gate Review track defect escape and first-time-right metrics?
Quality Gate Review monitors defect escape rates and first-time-right percentages as key quality indicators. These metrics are captured at each gate stage, aggregated into dashboards for sprint visibility, and used to identify process improvement opportunities. Tracking these metrics enables teams to measure and improve quality performance over time.
SKILL.md
rendered from the published skill — quoted content, verbatim
> Codex compatibility note:
>
> - Invoke repository skills with $skill-name in Codex; this mirrored copy rewrites legacy Claude /skill-name references.
> - Task tracker mandate: BEFORE executing any workflow or skill step, create/update task tracking for all steps and keep it synchronized as progress changes.
> - User-question prompts mean to ask the user directly in Codex.
> - Ignore Claude-specific mode-switch instructions when they appear.
> - Strict execution contract: when a user explicitly invokes a skill, execute that skill protocol as written.
> - Subagent authorization: when a skill is user-invoked or AI-detected and its protocol requires subagents, that skill activation authorizes use of the required spawn_agent subagent(s) for that task.
> - Do not skip, reorder, or merge protocol steps unless the user explicitly approves the deviation first.
> - For workflow skills, execute each listed child-skill step explicitly and report step-by-step evidence.
> - If a required
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.agents/skills/quality-gate-review/SKILL.md