quality-gates-audit

Audit pre-commit, pre-push, and CI/CD quality gates against an opinionated baseline.

3|5|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill quality-gates-audit-bensheridanedwards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-gates-audit
Source: https://github.com/BenSheridanEdwards/ArchitectPlaybook/tree/main/quality-gates-audit
Command: npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill quality-gates-audit-bensheridanedwards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often lack visibility into whether their pre-commit hooks, pre-push checks, and CI/CD pipelines actually enforce the quality gates they assume are in place. This Skill statically audits a repository against an opinionated baseline of quality gates and reports each gate as present, partial, missing, or violating its intended enforcement. ## Core Features & Use Cases - Lifecycle-stage gate audit: Evaluates pre-commit gates (hook runner, staged-file formatter/linter, type check, commitlint, secret scan), pre-push gates (full type check, lint, unit tests, build smoke), and CI gates (workflow presence, E2E tests, coverage thresholds, bundle-size budgets, accessibility, vulnerability and license scans, Lighthouse CI). - Two-phase read-only workflow: Writes findings.md, findings.json, snapshot.md, and metadata.json to .architect-audits/quality-gates-audit/, then optionally generates an implementation plan with exact install commands and config snippets — never modifying the project itself. - Non-Node fallback mode: When package.json is absent, switches to documentation-or-skill-repository mode and audits repository-native gates such as validator scripts, Git hooks, and CI workflows. - Use Case: Before a release, run the audit to discover that your pre-push hook never runs unit tests and your CI lacks a dependency vulnerability scan, then generate an ordered implementation plan to close those gaps. ## Quick Start Run /quality-gates-audit in the repository root to audit all quality gates and receive a Top 5 recommendations summary plus a full report on disk.

Frequently Asked Questions about quality-gates-audit

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

FAQPage Schema
How do I audit pre-commit and pre-push hooks in my repository?

Run /quality-gates-audit from the repository root. It statically inspects Husky or Lefthook configuration, lint-staged blocks, and hook scripts, then classifies each gate as present, partial, missing, or violation with evidence paths.

What CI/CD quality gates should a TypeScript project enforce?

The baseline expects a CI workflow that re-runs type check, lint, unit tests, and build on a clean checkout, plus coverage thresholds, dependency vulnerability scans, and optionally E2E tests, bundle-size budgets, accessibility checks, license compliance, and Lighthouse CI.

Does the quality gates audit work without a package.json?

Yes. When package.json is absent, the audit switches to documentation-or-skill-repository mode and checks repository-native gates such as validator scripts, local Git hooks, Conventional Commit enforcement, and CI workflows instead of stopping.

Will the audit modify my hooks or CI configuration files?

No. The audit is fully read-only and never executes gates, installs packages, or edits configuration. It only writes reports under .architect-audits/quality-gates-audit/ and can optionally generate a descriptive implementation plan for you to apply manually.

Why does a gate report partial or misconfigured instead of present?

A gate is partial when only some detection signals resolve, and misconfigured when enforcement is defeated, such as conflicting ESLint and Biome setups or a lint command that does not fail on warnings. The evidence array records exactly which signals matched.