agentleFS
Sign inStart free
MH4GFMH4GF/claude-code/.agents/skills/difit/SKILL.md

difit

Skill2 starsChanged 6 months agoMITView on GitHub

Ask the user for a code review through difit after code changes.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. yoshiko-pg/difit★ 3.2k47% same

    Wrote their own version · 0

    None found.

    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.

  • In this repository4 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 5 are distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before running commands, choose <difit-command> using the following rule:

    line 11
  2. Very specific:

    If command -v difit succeeds, use difit.

    line 13
  3. Very specific:

    If falling back to npx difit would require network access in a sandboxed environment without network permission, request escalated …

    line 15
  4. Distinctive:

    If the user leaves review comments, they are printed to stdout when the chosen difit command exits.

    line 17
  5. Distinctive:

    When review comments are returned, continue work and address them.

    line 18
  6. Distinctive:

    If the server is shut down without comments, treat it as "no review comments were provided." Restarting it is unnecessary.

    line 19
  7. Very specific:

    If there is something you want to tell the user when difit opens, attach it as startup comments with --comment.

    line 38
  8. Very specific:

    Use type: "thread" for each comment.

    line 47
  9. Distinctive:

    Write comment bodies in the language the user is using.

    line 48
  10. Very specific:

    Use position.side: "new" for lines that exist on the target side of the diff.

    line 49
  11. Very specific:

    Use position.side: "old" for lines that exist only on the deleted side.

    line 50
  12. Distinctive:

    Use range comments for issues that span multiple lines.

    line 51
  13. Very specific:

    Never copy secrets, tokens, passwords, API keys, private keys, or other credential-like material from the diff into --comment bodies or any …

    line 52

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

Difit

Overview

This skill requests a code review from the user using difit. Before running commands, choose <difit-command> using the following rule:

  • If command -v difit succeeds, use difit.
  • Otherwise, use npx difit.
  • If falling back to npx difit would require network access in a sandboxed environment without network permission, request escalated permissions and user approval before running it.

If the user leaves review comments, they are printed to stdout when the chosen difit command exits. When review comments are returned, continue work and address them. If the server is shut down without comments, treat it as "no review comments were provided." Restarting it is unnecessary. Manual verification of whether the page launched correctly is also unnecessary.

Commands

  • Review uncommitted changes before commit: <difit-command> .
  • Review the HEAD commit: <difit-command>
  • Review staging area changes: <difit-command> staged
  • Review unstaged changes only: <difit-command> working

Basic Usage:

<difit-command> <target>                    # View single commit diff. ex: difit 6f4a9b7
<difit-command> <target> [compare-with]     # Compare two commits/branches. ex: difit feature main

Optional Startup Comments

If there is something you want to tell the user when difit opens, attach it as startup comments with --comment. This is useful for review findings, explanations, and any context the user should see directly on the diff.

<difit-command> <target> [compare-with] \
  --comment '{"type":"thread","filePath":"src/foobar.ts","position":{"side":"old","line":102},"body":"line 1\nline 2"}' \
  --comment '{"type":"thread","filePath":"src/example.ts","position":{"side":"new","line":{"start":36,"end":39}},"body":"Range comment for L36-L39"}'
  • Use type: "thread" for each comment.
  • Write comment bodies in the language the user is using.
  • Use position.side: "new" for lines that exist on the target side of the diff.
  • Use position.side: "old" for lines that exist only on the deleted side.
  • Use range comments for issues that span multiple lines.
  • Never copy secrets, tokens, passwords, API keys, private keys, or other credential-like material from the diff into --comment bodies or any command-line arguments.

Including Untracked Files

For uncommitted changes, if files not yet added to git should also appear in the diff, add --include-untracked.

<difit-command> . --include-untracked

Constraints

Can only be used inside a Git-managed directory.

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