freeze-review
Skill1 starsChanged yesterdayMITView on GitHub
Use when a phase output is declared frozen: true and downstream phases consume it as ground truth without re-deriving (SD-3 Thinking → Auto boundary; OVERSEER-KIT-SPEC §6). Review frozen specs and contracts before Auto build phases depend on them. Default path is automated review with file + line citations for every finding; human escalation only for security, irreversibility, real money, or Tier-3 gates. For bounded review → fix → re-review until pass, use cursor/skills/freeze-review-loop/SKILL.md (/freeze-review-loop). Not automatic — invoke when a…
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/build-verification-required.mdcCursor rule
- .cursor/rules/check-ok-thinking.mdcCursor rule
- .cursor/rules/governance-sync.mdcCursor rule
- .cursor/rules/l1-checkpoints-consumer-owned.mdcCursor rule
- .cursor/rules/no-docs-only-pr-to-main.mdcCursor rule
- .cursor/rules/orchestrator.mdcCursor rule
- .cursor/rules/print-next-closeout.mdcCursor rule
- .cursor/rules/tier-authority.mdcCursor rule
- .cursor/rules/workspace-authority.mdcCursor rule
- build-verification-reviewSkill
- check-okSkill
- deploy-verification-reviewSkill
- freeze-review-loopSkill
- freeze-reviewSkill
- governance-syncSkill
- independent-second-reviewerSkill
- print-nextSkill
- workspace-statusSkill
- build-verification-reviewSkill
- check-okSkill
- deploy-verification-reviewSkill
- freeze-review-loopSkill
- governance-syncSkill
- independent-second-reviewerSkill
- knowtationSkill
- print-nextSkill
- workspace-statusSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
Use when a phase output is declared frozen: true and downstream phases consume it as ground truth without re-deriving (SD-3 Thinking → Auto …
- Distinctive: line 22
Before Tier 3 action consumes a frozen artifact (merge, staging push, live flip)
- Very specific: line 70
Every finding must include path:line so the operator can verify — never trust uncited review output.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Freeze-step review skill
Use when a phase output is declared frozen: true and downstream phases consume it as ground truth
without re-deriving (SD-3 Thinking → Auto boundary; OVERSEER-KIT-SPEC §6).
Purpose
Review frozen specs and contracts before Auto build phases depend on them. Default path is automated review with file + line citations for every finding; human escalation only for security, irreversibility, real money, or Tier-3 gates.
Read first
docs/OVERSEER-KIT-SPEC.md§6 — Freeze-Contract review policypolicy/freeze-contract.schema.yaml(K5) — phase output declarations.overseer/config.yaml→freeze_contract.human_escalation
When to run
- Roadmap step marked Thinking → Auto and
{step}acontract artifacts are Muse/Git committed - Any artifact listed as
frozen: truein a phase freeze block - Before Tier 3 action consumes a frozen artifact (merge, staging push, live flip)
- Ad-hoc / side research via
/check-ok(scaffoldsdocs/reviews/then this gate)
Review checklist
- Ground-truth edge: does a later phase treat this output as truth without re-deriving?
- Completeness: interfaces, fail-closed rules, test matrix present?
- Security: injection surfaces, secrets, scope leaks?
- Irreversibility / real money: migrations, deletes, billing?
- Tier 3 linkage: does this artifact gate merge, staging, or live gates?
Verdicts
| Verdict | Meaning |
pass | No blocking findings; record review stamp |
findings | Cited list; resolve or escalate per config |
blocked | Human required before downstream Auto build |
CLI (when K5 lands)
/path/to/overseer-kit/cli/ok review --freeze <path> --dry-run
/path/to/overseer-kit/cli/ok review --freeze <path>Multi-round loop (optional)
For bounded review → fix → re-review until pass, use cursor/skills/freeze-review-loop/SKILL.md
(/freeze-review-loop). Not automatic — invoke when a frozen spec must clear before {step}b Auto build.
After Auto build (honesty gate)
Freeze review guards the spec. cursor/skills/build-verification-review/SKILL.md
(/build-verification-review) guards the implementation — run before marking the phase DONE.
Manual/opt-in today; required by SD-3 discipline even when not enforced by CLI.
Escalate to human when
security— auth, scope, secrets, injectionirreversible— data deletion, non-revertible migrationsreal_money— billing, live model spendgates_tier3— artifact gates merge, staging push, or live flip
Everything else: agent resolves or reports without a human stop.
Must cite
Every finding must include path:line so the operator can verify — never trust uncited review output.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

