Gate
Pre-PR gate — run the full readiness check before opening a pull request. Use when the developer is about to push or open a PR, or asks "is this ready?". Orchestrates build, tests, review, security, migration safety, and commit/doc hygiene into one go/no-go verdict.From its SKILL.md
npx -y skills add Brayanhenaor/ai-standards --skill gateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.1 KB, as published. Nobody here has run it
Gate — pre-PR readiness
One orchestrated pass that answers a single question: is this change ready to open as a PR? Compose the other skills; don't re-implement them. Report a clear go / no-go with the blockers.
For the full PR review report — context-gathering, findings by severity, ADR recommendation, and
an evidence file to attach to the PR — use pre-pr. gate is the terse go/no-go; pre-pr is the
detailed reviewer.
Run, in order
- Build & tests (
verify) — it compiles and the test suite passes. A red build is an instant no-go. - Review (
review --diff) — clean-code and correctness audit of the change. Surface[CRITICAL]findings as blockers. - Security (
security-audit --diff) — anyCRITICAL/HIGHfinding is a blocker. - Migration safety (
migrate) — if the diff touches schema/migrations, check it's safe and reversible. - Hygiene — secrets/
.env/generated files not staged; commits follow Conventional Commits; README/docs updated if config, env vars, endpoints, or deployment changed.
Verdict
Report concisely:
GATE: GO / NO-GO
✓ build & tests ✓/✗
✓ review (clean code) ✓/✗ — N critical
✓ security ✓/✗ — N critical/high
✓ migration safety ✓/✗ / n/a
✓ hygiene & docs ✓/✗
Blockers:
- [the specific things that must be fixed before the PR]
- NO-GO if any blocker exists. List exactly what to fix — don't soften it.
- GO only when all checks pass. Don't wave a change through to be agreeable; the gate's value is that it says no when it should.
- Don't fix things here — gate reports. Hand specific fixes back to the relevant skill.
Reply in the developer's language; keep code and identifiers in English.