resolve-repository-state
Skill23 starsChanged 51 days agoMITView on GitHub
Resolve an explicit Normalized Repository State contradiction. This is the sole writer allowed to update frozen repository facts or accepted decisions. Triggers: "resolve repository state", "resolve contradiction", "update a frozen repository fact".
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- template/AGENTS.mdAGENTS.md
- audit-docsSkill
- audit-prSkill
- batch-schedulerSkill
- discover-repository-stateSkill
- execute-phaseSkill
- fold-findingsSkill
- init-workspaceSkill
- log-sessionSkill
- orchestration-envelopeSkill
- phase-contractSkill
- pre-execution-reviewSkill
- product-auditSkill
- review-a11ySkill
- review-brandSkill
- review-changeSkill
- review-codeSkill
- review-debtSkill
- review-designSkill
- review-implementationSkill
- review-perfSkill
- review-securitySkill
- review-seoSkill
- review-verifySkill
- skill-lintSkill
- triage-issueSkill
- unit-laneSkill
- verification-contractSkill
- workflow-statusSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Read the agent guide, documentation map, frozen ledger, and the requested contradiction before deciding anything.
- Distinctive: line 34
Read the frozen ledger and the contradiction row named by the user.
- Distinctive: line 35
Verify both the frozen fact's evidence and the proposed new evidence.
- Very specific: line 37
If human input is required, update the contradiction row with the exact missing evidence or decision, keep snapshot status contradicted, …
- Distinctive: line 69
If human input is required:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Resolve Repository State
Resolve evidence conflicts explicitly and publish the next frozen snapshot.
Turn contract
✓ A named contradiction and both evidence sources were read
✓ The disposition is accepted, rejected, or needs-input
✓ Accepted/rejected results publish a frozen snapshot; needs-input stops without freezing
✓ No unrelated fact or decision changed
✓ The closing → Next: block is printed lastStep 0 — Discover the project (always first)
Read the agent guide, documentation map, frozen ledger, and the requested contradiction before deciding anything.
Process
- Read the frozen ledger and the contradiction row named by the user.
- Verify both the frozen fact's evidence and the proposed new evidence.
- Choose one result: accept new evidence, reject it, or request human input.
- If human input is required, update the contradiction row with the exact
missing evidence or decision, keep snapshot status
contradicted, and stop without incrementing the snapshot identifier or publishing a frozen snapshot. - For an accepted result, supersede the fact or decision with a new row that cites both evidence sources. For a rejected result, retain the fact and record why.
- For accepted or rejected results only, update the contradiction row,
increment the snapshot identifier, set status to
frozen, and record the next frozen snapshot's source revision.
Guardrails
- This skill is the sole writer for updates to frozen facts and accepted decisions.
- A consumer may propose a contradiction but never resolve it inline.
- Inference and documentation alone are insufficient to update a fact.
Portability
Without a slash menu, open this file and follow its process in a fresh turn.
Relationship to other skills
Consumes contradictions from every workflow role and produces the snapshot that
discovery, planning, execution, review, and audit reuse. The contradiction's
Reported by field identifies the interrupted role to resume; resolution never
defaults a review, audit, or status interruption to planning.
Done when
The contradiction has a recorded disposition, and either the next frozen snapshot is internally consistent or the missing human input is explicit.
If human input is required:
→ Next: provide the requested evidence or decision — resolution cannot continue yet
· evidence supplied → rerun /resolve-repository-state <contradiction-id>
Otherwise:
→ Next: resume the interrupted workflow named by Reported by — continue from the resolved snapshot
· planning was interrupted → /unit-lane <slug>
· implementation was interrupted → /execute-phase <NN>
· review, audit, or status was interrupted → rerun that same skill
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.

