agentleFS
malinskibeniaminmalinskibeniamin/skills/visual-recap/SKILL.md

visual-recap

Skill4 starsChanged 10 days agoMITView on GitHub

Create an interactive visual recap for a PR, branch, commit, or diff.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 1

    Distinctive

    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
  1. Very specific:

    Before recap, read references/agent-native-recap.md.

    line 9
  2. Very specific:

    Only explicit /visual-recap creates/links the named PR/branch/commit/diff.

    line 18
  3. Distinctive:

    If target has no visual structure, return that evidence instead of inventing a recap.

    line 21

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “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

Translate upstream npx @agent-native/core to bunx @agent-native/core.

Before recap, read references/agent-native-recap.md; it owns create-visual-recap, never-inline, Plan MCP URL, diff blocks, redaction, security, local privacy, feedback. Apply host compatibility before upstream tool, delegation, publication, or installation recipes.

Load only when needed: references/connection.md for connector/reconnect/fallback; references/local-files.md for local-only; references/wireframe.md for visible UI diffs.

Overlay

  • For meaningful causal structure, follow ../shared/intent-map.md; ground every node/edge in the diff, label inference, and reuse the recap diagram surface.
  • Only explicit /visual-recap creates/links the named PR/branch/commit/diff; /commit-push-pr and /go never invoke automatically.
  • For meaningful architecture/data flow, /excalidraw-diagram creates .excalidraw plus PNG/SVG. Agent-Native remains primary: embed supported media, else diagram block plus source/export paths. Use Mermaid for simple graph/unavailable canvas.
  • Ground in real diff, redact secrets, never infer beyond changed lines.
  • If target has no visual structure, return that evidence instead of inventing a recap.

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.