revisit
Skill4 starsChanged 25 days agoMITView on GitHub
Reopen an earlier decision that no longer fits, by reasoning through a new decision that supersedes it.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- duthaho/skillhubtheir own version, first seen Oct 31, 2026
- mik2win/foureyestheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- duthaho/skillhub★ 9same name
- mik2win/foureyes★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 16
Run reazon status. If the user didn't name a decision, show the accepted and built ones (number, title) and ask which one with …
- Distinctive: line 19
Read the old decision file in full.
- Very specific: line 23
Run reazon new --title "<question>" --supersedes <old id> and follow the decide guide from Framing.
- Distinctive: line 27
When the new decision is accepted, the helper marks the old one superseded and links both.
≈ “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
Reazon revisit
A past decision stays as history. Revisiting creates a new decision that replaces it once accepted, so the record shows how the thinking changed.
The helper is node "${CLAUDE_PLUGIN_ROOT}/bin/reazon.mjs" <command> --cwd "<absolute project folder>",
written below as reazon <command>. Quote paths. It prints JSON; on "ok": false,
explain the error and stop. Don't edit Reazon files by hand as a fallback.
- Run
reazon status. If the user didn't name a decision, show the accepted and built ones (number, title) and ask which one with AskUserQuestion (headerRevisit,multiSelect: false, up to four options). - Read the old decision file in full.
- In chat, show the old decision's Problem, choice, and the learner's Why as a short recap. Then ask, as ▶ Your turn: what changed that makes this decision not fit anymore? Wait.
- Run
reazon new --title "<question>" --supersedes <old id>and follow the decide guide from Framing. What matters must include what changed, and if the change is about the project's goals, update the brief first in the learner's words. The old choice is one of the options, evaluated against the new list. - When the new decision is accepted, the helper marks the old one superseded and links both. Mention that in the ✓ Unlocked block.
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.

