quality-gates

Pre-commit quality gates enforce lint cleanliness and test presence by running hook checks before a commit is finalized. This skill enables pre-commit and commit-msg hooks to validate all changed files against defined gates automatically.

A pre-commit hook should enforce task existence, test presence, lint cleanliness, ADR presence for architecture changes, a 500 LOC diff limit, absence of hardcoded secrets, updated documentation, and conventional commit formatting.

You require an ADR for architectural changes by enabling a commit gate that detects architecture modifications and blocks the commit until an Architecture Decision Record is present.

Yes, you can block large diffs using the 500 LOC diff rule gate. It measures the lines of code changed and rejects commits exceeding the limit while providing guidance on handling exceptions.

You enforce conventional commit formatting by applying a commit-msg hook gate. It validates the commit message structure, ensuring it includes a task identifier and follows conventional commit standards before acceptance.

You prevent hardcoded secrets by applying a pre-commit secret detection gate. It scans all changed files for secrets and blocks the commit if any hardcoded credentials are found.