aibom-change-quality-gates

Run repo-specific quality gate workflows to validate code changes.

Updated Aug 27, 2026

Search Tags:#automation #quality gates #risk-assessment #pull-request #code-change #diff-analysis #contract-checks

Ready to run

npx skills add https://github.com/SameerG7/synthesis-hackathon-aibom --skill aibom-change-quality-gates

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aibom-change-quality-gates
Source: https://github.com/SameerG7/synthesis-hackathon-aibom/tree/main/.codex/skills/aibom-change-quality-gates
Command: npx skills add https://github.com/SameerG7/synthesis-hackathon-aibom --skill aibom-change-quality-gates

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This feature validates code changes by running a targeted suite of invariants, contract checks, and impact tests to prevent regressions before merging.

Core Features & Use Cases

Discover change scope and surface potential risk areas across the repository.
Run lightweight quality gates by default and escalate to stricter checks when risk is detected.
Provide escalation paths and traceability for failed checks to guide remediation.

Quick Start

Run the quality gates against the changed files using the provided script.

Frequently Asked Questions about aibom-change-quality-gates

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

FAQPage Schema

How do I run quality gates on a pull request to detect contract issues?▼

Run quality gates on a pull request by executing a repo-specific workflow script to validate code changes, detect structural invariants, and identify contract issues before merging. The workflow coordinates diff discovery and impact tests to prevent regressions.

What is a targeted quality gate workflow for code changes?▼

A targeted quality gate workflow validates code changes by running a suite of invariants and impact tests. It discovers the change scope across the repository, surfaces risk areas, and provides traceability for failed checks to guide remediation.

How do quality gates decide when to escalate from quick to strict checks?▼

Quality gates run lightweight checks by default and escalate to stricter validation when risk is detected during diff discovery. The workflow assesses the change scope and surfaces potential risk areas to determine if strict contract checks are necessary.

Can I use diff analysis to prevent regressions before merging code updates?▼

Yes, diff analysis prevents regressions by identifying changed files and running targeted invariants. The quality gate workflow discovers the change scope, runs impact tests, and reports failures with traceability to guide remediation before merging.

What do I need to run repo-specific quality gates for risk assessment?▼

You need the run_quality_gates.sh script, quality invariants defined in references/quality-invariants.md, and an impacted-test mapper. These components coordinate to execute risk assessment and report validation results for code updates.