Gate repository-changing Agent work through the read-only repo-governance preflight JSON contract. Use before fixing bugs, adding features, editing code, running task tests, committing, or preparing a pull request, and when interpreting unmanaged, misconfigured, blocked, or disconnected-hook states.
Scanned 9/28/2026
Install to Claude Code
npx -y skills add CoaseEdge/repo-governance --skill repo-governance-agent-gate --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Repo Governance Agent Gate?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/coaseedge-repo-governance-agent-gate)More formats (shields.io, HTML) on the badges page.
---
name: repo-governance-agent-gate
description: Gate repository-changing Agent work through the read-only repo-governance preflight JSON contract. Use before fixing bugs, adding features, editing code, running task tests, committing, or preparing a pull request, and when interpreting unmanaged, misconfigured, blocked, or disconnected-hook states.
---
# Repository Governance Agent Gate
1. Run `repo-governance preflight --json` in the task working directory before repository-changing work.
2. Read [references/playbook.md](references/playbook.md); in the source repository, use `playbooks/repo-governance-agent-gate.md`.
3. Decide from `status`, `repoState`, and `recommendedAction` together. Never use `ok` alone as write permission.
4. Continue writes only for `status: "succeeded"` with `repoState: "managed"`.
5. Re-run preflight after an approved bootstrap or Hook repair. Use `repo-governance prepare-pr --json` before pull request work.
Do not infer a preset, repair configuration on your own, write remote state, or reimplement RG001-RG005, engine checks, Hook discovery, or path policy.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!