agentleFS
Sign inStart free
MFaizR77MFaizR77/turnback/skills/diff-turn/SKILL.md

diff-turn

Skill1 starsChanged 29 days agoMITView on GitHub

Show the file changes made during one agent turn recorded by Turnback. Use when the user asks what a specific turn changed.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

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

    Use the turn ID in the user's request or invocation arguments.

    line 7
  2. Very specific:

    Call diff_turn with that turn and patch true.

    line 8

≈ “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
  1. Use the turn ID in the user's request or invocation arguments. If none is given, call list_turns from the turnback MCP server with limit 1 and use that turn's ID. Always pass workspace set to the current project directory.
  2. Call diff_turn with that turn and patch true.
  3. Summarize the changes per file in a few lines, then show the patch. If the result says truncated, say so. For the full patch, resolve the installed plugin root from PLUGIN_ROOT (Codex) or CLAUDE_PLUGIN_ROOT (Claude Code) and run node <plugin-root>/dist/cli.js diff <turn> in the project directory, quoting the resolved path for the current shell. If the plugin root cannot be resolved, report that the CLI fallback is unavailable.

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.

Check your setup, free