light-review-existing-diffs
Skill0 starsChanged 9 months agoMITView on GitHub
Perform a quick quality pass on current diffs to surface risky areas, ensure polish, and fla...; keywords: debug, review, test, fix. Use only on explicit request; skip in routine implementation discussions.
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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
- Distinctive: line 21
Verify naming, formatting, and imports follow project standards
- Distinctive: line 22
Check that tests or documentation were updated when behavior changed
- Distinctive: line 26
Document any quick fixes you can apply immediately
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.
Files
Light Review Existing Diffs
Overview
Perform a quick quality pass on current diffs to surface risky areas, ensure polish, and flag follow-up actions for deeper review.
Steps
- Scan recent changes
- List open branches or pending commits requiring review
- Skim side-by-side diffs focusing on new or modified files
- Note files or modules with large or complex edits
- Assess quality signals
- Watch for TODOs, debug code, or commented blocks needing cleanup
- Verify naming, formatting, and imports follow project standards
- Check that tests or documentation were updated when behavior changed
- Flag next actions
- Mark sections that warrant full review or pair programming
- Capture questions or uncertainties to raise with the author
- Document any quick fixes you can apply immediately
Review Checklist
- High-risk files identified
- Debugging artifacts removed or flagged
- Style and conventions validated
- Tests/docs updates confirmed or requested
- Follow-up items recorded for deeper review
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- emaraschio/cursor-commands★ 973% 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 repository31 other files it gives its agents.
- accessibility-auditSkill
- add-documentationSkill
- add-error-handlingSkill
- address-github-pr-commentsSkill
- clarify-taskSkill
- code-reviewSkill
- create-prSkill
- database-migrationSkill
- debug-issueSkill
- deslopSkill
- diagramsSkill
- docker-logsSkill
- fix-compile-errorsSkill
- fix-git-issuesSkill
- generate-api-docsSkill
- generate-pr-descriptionSkill
- git-commitSkill
- git-pushSkill
- lint-fixSkill
- lint-suiteSkill
- onboard-new-developerSkill
- optimize-performanceSkill
- overviewSkill
- refactor-codeSkill
- roadmapSkill
- run-all-tests-and-fixSkill
- security-auditSkill
- security-reviewSkill
- setup-new-featureSkill
- visualizeSkill
- write-unit-testsSkill
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.

