quality-gate

Generate a Quality Gate Report linking requirements to verification evidence.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/terraphim/terraphim-skills --skill quality-gate-terraphim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-gate
Source: https://github.com/terraphim/terraphim-skills/tree/main/skills/quality-gate
Command: npx skills add https://github.com/terraphim/terraphim-skills --skill quality-gate-terraphim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates turning a change/PR into a go/no-go decision by generating a centralized Quality Gate Report that aggregates verification evidence across code review, static analysis, requirements traceability, security, performance, acceptance testing, and UI considerations.

Core Features & Use Cases

  • Evidence-based gating: compile findings from code review, static analysis, security audits, performance checks, and acceptance criteria, all linked to requirements.
  • Traceability: map each requirement to verification evidence and tests to enable auditability.
  • Actionable outputs: produce a concise report with follow-ups and suggested remediation for failed gates.

Quick Start

  • Provide the change context (PR link/ID) and explicit scope.
  • Run the quality-gate tool in CI or locally to generate the report.
  • Review the produced Quality Gate Report and act on blockers or follow-ups.

Frequently Asked Questions about quality-gate

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

FAQPage Schema
How do I automate PR quality gates with evidence from code review and static analysis?

You can automate PR quality gates by generating a centralized Quality Gate Report that aggregates verification evidence across code review, static analysis, security, performance, and acceptance testing, linking findings directly to requirements.

What is requirements traceability in a pull request quality gate?

Requirements traceability in a quality gate maps each requirement to verification evidence and tests, enabling auditability and ensuring code changes satisfy acceptance criteria before merging.

How do I generate a Quality Gate Report for a pull request?

Provide the change context, such as the PR link or ID, and the explicit scope, then run the quality-gate tool in CI or locally to produce a structured report with blockers and suggested remediation.

Can I enforce an evidence-based workflow for PR code review and acceptance testing?

Yes, enforcing an evidence-based workflow requires inputs like change context and scope to output a structured report linking requirements to tests, static analysis findings, and security considerations.

Does the quality gate report include security and performance findings?

Yes, the Quality Gate Report aggregates findings from security audits and performance checks alongside code review, static analysis, requirements traceability, acceptance testing, and UI considerations.

What is the best way to map requirements to verification evidence for a go/no-go decision?

The best way to map requirements to verification evidence is using a centralized Quality Gate Report that compiles findings from multiple checks and produces actionable follow-ups for failed gates.