aegis-quality-gates

Automate quality gates by executing a canonical 10-gate verification sequence that runs build, lint, tests, and security scans, emitting a structured JSON verify-report and exiting non-zero on failure. It reads per-project thresholds from presets to support both quick pre-commit runs and full end-to-end builds.

An end-to-end build verification sequence includes 10 gates: build, tsc, lint, tests, aegis-scan, brutaler-anwalt, lighthouse, skillforge-validate, briefing-coverage, and residue-check. Each gate executes real commands in a defined order to ensure code readiness before commit or deployment.

A quality gate pipeline reports verification results by emitting a structured .aegis/verify-report.json alongside a Markdown summary. These outputs streamline reporting and handover by documenting the canonical 10-gate execution status and identifying any failed checks.

Yes, you can configure per-project quality gate thresholds by using presets. The verification sequence reads these preset configurations to determine acceptable thresholds, allowing the same 10-gate pipeline to support both pre-commit quick runs and full end-to-end builds.

Enforce software security and code quality by integrating an automated 10-gate verification sequence into your pre-commit and deployment pipelines. It runs checks like aegis-scan, lighthouse, and lint, exiting non-zero when any gate fails to block unverified changes from reaching production.

A build pipeline exits with a non-zero status during gate verification when any of the 10 canonical gates fail. This mechanism ensures unverified changes are blocked, preventing code that does not meet the configured per-project thresholds from being committed or deployed.