agentleFS
mtarcuremtarcure/claude-vibe-squad/.agents/skills/differential-review/SKILL.md

differential-review

Skill220 starsChanged 20 days agoMITView on GitHub

Use when a proposed change claims to preserve or intentionally alter behavior and the delta must be proven between baseline and candidate—run both states, predict each observable shift, then compare return values, persistence, emitted events, logs, exit codes, wire formats, timing, errors, empty cases, and boundaries. This is execution-based comparison, not changed-line inspection or pixel diffing.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use json-canvas, obsidian-bases and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • wangzhuofengSkill

    json-canvas

    Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.

    Also in 3 projects that use this

  • wangzhuofengSkill

    obsidian-bases

    Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.

    Also in 3 projects that use this

  • GoogleSkill

    ponytail

    Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

    Also in 3 projects that use this

  • GoogleSkill

    improve-codebase-architecture

    Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

    Also in 3 projects that use this

  • +3 more from google

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat every unpredicted delta as a finding until explained.

    line 15
  2. Distinctive:

    Every moved surface is listed with predicted versus observed behavior.

    line 23

“Common” is measured: kept by at least 6 in 10 of the 13 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

Differential Review

Review a change by comparing behavior before and after, rather than by reading the new code in isolation.

Steps

  1. Build the two states: base and head. Anything that cannot be built in both states cannot be differentially reviewed — say so instead of guessing.
  2. Enumerate observable surfaces the change could move: return values, persisted rows, emitted events, logs, exit codes, wire formats, timing, and error text.
  3. For each surface, predict the intended delta from the change's stated intent, then measure the actual delta.
  4. Treat every unpredicted delta as a finding until explained. Silent behavior changes are the class this method exists to catch.
  5. Pay special attention to the unchanged-looking paths: refactors that preserve the happy path frequently move error, empty, and boundary behavior.
  6. Where a surface cannot be measured, construct the smallest differential test that would measure it, and note the gap if the test is out of scope.
  7. Compare against a scalar or previous reference implementation where one exists — vectorized, cached, or rewritten code is unverified without it.
  8. Record deltas that are intended-but-breaking separately from deltas that are unintended; they need different decisions from the operator.

Acceptance

  • Base and head were both built or run; if not, the review states that it is analysis-only.
  • Every moved surface is listed with predicted versus observed behavior.
  • Unpredicted deltas are reported as findings or explicitly explained.
  • Error, empty, and boundary paths are covered, not just the happy path.
  • Intended-breaking and unintended changes are distinguished.

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.