revisit SKILL.md skillA
revisit from imagile-dev/claude-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add imagile-dev/claude-plugins/revisit@git:20261020.ce5808aPins git:20261020.ce5808a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- imagile-dev/claude-plugins
- Path
plugins/imagile/skills/revisit/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261020.ce5808a, committed Oct 20, 2026
- Size
- 2,203 bytes
- Repository stars
- 3
- License
- MIT
Review the decisions agents logged in AGENT_DECISIONS.md in one batch, then keep, promote to a principle, or reverse each. Use for revisit or review decisions.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Revisit Agents don't ask about every decision. They log it and keep shipping. This skill is the other half: the human reviews the log in batches, when it suits them. The log only holds open decisions, so it stays short. ## Recording a decision (every agent, every skill) Append to `AGENT_DECISIONS.md` at the repo root under `## Open`, in the same PR as the code it affects: ```markdown - **[What was decided, in one line.]** Optimizing for: [the quality it favors, and the principle it leaned on]. Gave up: [the cost]. Alternative: [the option not taken]. Where: `path/or/area`, #PR. ``` Log only what a reasonable maintainer might decide differently. Don't log what a principle or rule already settled. When unsure whether to log, log. ## Running a revisit 1. Read `AGENT_DECISIONS.md` and the current CLAUDE.md principles. 2. Group the open entries by theme. Inside a group, put the ones that most affect users or the architecture first. 3. Present one group at a time in chat. For each entry, one line, with your recommendation: - **Keep**: accepted as is. The entry is deleted. - **Promote**: a pattern worth stating. Write or sharpen a principle with …
Read the whole file at its exact version.
How to install
mdr add imagile-dev/claude-plugins/revisit@sha256:f45a0bdcbd957e66The line at the top of this page pins the label git:20261020.ce5808a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_a3amvv7fvx7limug)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 20, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2203 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
imagile-dev/claude-plugins · 3 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_a3amvv7fvx7limug GET https://markdownregistry.com/api/v1/resolve?ref=imagile-dev/claude-plugins/revisit GET https://markdownregistry.com/api/v1/blob/f45a0bdcbd957e664fb5336a81913df079cce3eb31ab8dd63c0be954b766f59e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from imagile-dev/claude-plugins
Every file in imagile-dev/claude-plugins