agentleFS
Sign inStart free
dprakash2101dprakash2101/dotnet-production-agent-skills/skills/diff-review/SKILL.md

diff-review

Skill4 starsChanged 51 days agoMITView on GitHub

Review the final working-tree diff for scope, regressions, secrets, and accidental changes. Use before declaring code-changing work complete or before staging a commit.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use test-design.

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.
  • shabarabaSkill

    test-design

    Automatically design comprehensive E2E test cases for newly implemented vibing.nvim features. Use immediately after completing feature implementation (Phase 5.4) and before running E2E tests. Generates test scenarios covering Happy paths, Error cases, Edge cases, and Integration points with priority ranking (Critical/High/Medium/Low) and ready-to-use test code templates using e2e_helper.lua.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Check for accidental deletion, unrelated formatting/renaming/refactoring, generated artifacts, debug code, commented-out code, secrets, …

    line 18

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

Diff review

Inspect, at minimum:

git status --short
git diff --stat
git diff

Also inspect staged changes when anything is staged. For every changed file ask: why did this file change, and how does it serve the request?

Check for accidental deletion, unrelated formatting/renaming/refactoring, generated artifacts, debug code, commented-out code, secrets, configuration drift, unintended public/API behavior, over-broad shared changes, missing tests, and user modifications that predated the task.

Revert only accidental agent-created changes, and only when ownership is clear. Never discard or overwrite user changes because they are unrelated. If changes overlap and cannot be safely separated, stop and explain the conflict.

Finish when the requested behavior is present, unrelated behavior is preserved, appropriate tests/validation are complete or honestly reported, and no unnecessary file remains changed. Stop there; do not continue cleanup.

Inspect relevant untracked files separately: ordinary git diff does not include them. Check staged and unstaged changes and assess generated or binary files when they are part of the requested deliverable.

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