agentleFS
Lethe044Lethe044/agentskill-kit/skills/json-diff/SKILL.md

json-diff

Skill48 starsChanged 17 days agoMITView on GitHub

Compares two JSON files structurally and lists added, removed and changed values with their full paths. Use when the user asks what changed between two API responses, config files, fixtures or package manifests.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    If identical is true, say so and stop.

    line 35
  2. Distinctive:

    Call out type changes (for example a number that became a string), they cause the subtle bugs.

    line 37

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

JSON diff

A structural comparison that ignores key order and formatting, which a plain text diff cannot do.

When to use

  • Two API responses should be the same but a test fails.
  • A config or lock file changed and the user wants to know exactly which values moved.
  • Comparing a fixture with the output of the code that is supposed to produce it.

How to run

python scripts/json_diff.py old.json new.json

Output

JSON with identical (boolean), count and changes. Every change has a path (for example users[1].email), a change of added, removed or changed, and the old and new values where they apply. The exit code is 1 when the files differ, 0 when they match.

Reading the result

  1. If identical is true, say so and stop.
  2. Group the changes by the first path segment so the user sees which area moved.
  3. Call out type changes (for example a number that became a string), they cause the subtle bugs.
  4. Arrays are compared by position. If order is not meaningful, tell the user the diff may be noisy.

Errors

A missing file exits with code 2. Invalid JSON exits with code 3 and names the file.

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.