agentleFS
gtrabancogtrabanco/agentic-workflow/skills/resolve-repository-state/SKILL.md

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".

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
  1. Distinctive:

    Read the agent guide, documentation map, frozen ledger, and the requested contradiction before deciding anything.

    line 29
  2. Distinctive:

    Read the frozen ledger and the contradiction row named by the user.

    line 34
  3. Distinctive:

    Verify both the frozen fact's evidence and the proposed new evidence.

    line 35
  4. Very specific:

    If human input is required, update the contradiction row with the exact missing evidence or decision, keep snapshot status contradicted, …

    line 37
  5. Distinctive:

    If human input is required:

    line 69

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 last

Step 0 — Discover the project (always first)

Read the agent guide, documentation map, frozen ledger, and the requested contradiction before deciding anything.

Process

  1. Read the frozen ledger and the contradiction row named by the user.
  2. Verify both the frozen fact's evidence and the proposed new evidence.
  3. Choose one result: accept new evidence, reject it, or request human input.
  4. 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.
  5. 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.
  6. 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.