scope-gate-setuplisted
Install: claude install-skill Snowfly0709/claude-scope-gate
# Discover and confirm this repository's invariants
`scope-gate` can only block what it knows about. This skill produces the thing it
reads: a short list of boundaries **this** repository must not cross, each one
confirmed by a human in language they actually understand.
Run once per repository. Re-run when a confirmed invariant turns out to be wrong.
## What you are looking for
An invariant is a rule that holds across the codebase and whose violation is a
release blocker rather than a bug — usually one of:
| Class | The question it answers |
|---|---|
| Credential handling | Whose key pays, and where may a secret travel? |
| Reachability | Who is allowed to reach this, and what proves it? |
| Exposure | What happens when something becomes selectable by a user? |
| Fail direction | When a check cannot complete, does it open or close? |
| Registry completeness | Adding one thing means adding it in N places — which N? |
| Data classification | Which data may leave which boundary? |
You are not looking for style rules, naming conventions, or anything a linter
already enforces. If a linter can catch it, it is not an invariant.
## Step 1 — Look for invariants that already exist
Most mature repositories already wrote these down. **Ingest that corpus; do not
start a competing list.** Check, in order:
- `harness/guides/rules/`, `docs/adr/`, `docs/architecture/`
- `.cursor/rules/`, `.github/CONTRIBUTING.md`
- `AGENTS.md`, `CLAUDE.md`, and anything they link to
- `README` file