diff-review
Skill2 starsChanged 4 months agoNo licenceView on GitHub
Review local git diffs for bugs, security issues, regressions, external findings, code quality, devex, feature gates, and maintainability before pushing to origin — with root cause analysis, codebase-aware context, branch-total re-review, invariant/variant proof, optional deep/harsh dual-pass review, executor-ready remediation planning, and iterative turn-based tracking. Use this skill whenever the user asks to review a diff, check changes before pushing, review staged changes, compare branches, run a pre-PR review, run a deep review, run a harsh/thermonuclear review, re-review after fixes, check review status, triage GitHub/Devin/CI findings, create fix plans for review findings, or says things like "review my changes", "check my diff", "what did I break", "run the review again", or "did I fix the issues".
19 other projects use a version of this.
Adopted by
Most recently taken up by
- moisesrj97/skillstheir own version, first seen Nov 8, 2026
- pranataa-labs/Workflow-Mastertheir own version, first seen Nov 8, 2026
- MidnightDarling/collatetheir own version, first seen Nov 1, 2026
- Hakkadaikon/hymmetheir own version, first seen Oct 26, 2026
- scottlivingston/claude-skillstheir own version, first seen Oct 25, 2026
- rosslevinsky/portable-agent-skillstheir own version, first seen Oct 15, 2026
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.
shabarabaSkilltest-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
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- ClickHouse/ClickHouse★ 51ksame name
- ComplyEaze/bridge★ 35same name
- lamemustafa/bridge★ 35same name
- rosslevinsky/portable-agent-skills★ 12same name
- yasunori0418/skills★ 9same name
- MidnightDarling/collate★ 8same name
- dprakash2101/dotnet-production-agent-skills★ 4same name
- Lixiuxiu559/AgentForge★ 4same name
- pranataa-labs/Workflow-Master★ 2same name
- hmu332233/skills★ 1same name
9 more not listed
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 repository6 other files it gives its agents.
- ai-consultantSkill
- architecture-standardsSkill
- fallowSkill
- notion-demandSkill
- repo-auditSkill
- spec-driven-developmentSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
33 rules. 0 are common, 22 are distinctive, and 11 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
22
Distinctive
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“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.
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
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.