diff-check
Skill1 starsChanged 8 months agoMITView on GitHub
Author's cleanup checklist before committing or submitting a PR. Use before any commit or PR to ensure code is clean, focused, and ready for review. Checks for debug code, secrets, redundant changes, and scope creep.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- global/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- browser-toolsSkill
- clone-with-hashSkill
- decompose-taskSkill
- ios-safari-debugSkill
- market-researchSkill
- publish-artifactSkill
- spec-templateSkill
The file
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 13
Before marking a PR ready for review
- Distinctive: line 14
After implementing changes, before requesting review
- Distinctive: line 53
Do NOT make changes automatically—report for human confirmation
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Diff Check
Perform routine cleanup and validation before committing code or submitting a PR.
When to Use
- Before any
git commit - Before marking a PR ready for review
- After implementing changes, before requesting review
Checklist
1. Scope & Focus
- Changes are within the scope of the task/PR
- No redundant or unnecessary code changes
- No unrelated formatting or whitespace changes
2. Code Cleanup
- No debugging code left in (console.log, print, dbg!, etc.)
- No testing stubs or mock data in production code
- No commented-out code blocks (unless intentionally preserved)
- No self-explanatory comments that clutter code
3. Security
- No secrets, API keys, or credentials exposed
- No hardcoded local file paths (e.g., /home/user1/...)
- No sensitive information in comments or logs
4. Consistency
- Code follows project lint/format rules
- Naming conventions are consistent
- Import statements are organized
5. Plan Alignment
- Relevant checkboxes in plan.md are marked complete
- Commit message is clear and follows conventions
6. Branch Health (PR only)
- Synced with main/target branch
- No merge conflicts
- CI checks pass (if applicable)
Process
- Review all staged/modified files
- Walk through checklist above
- Report any issues found with recommended fixes
- Do NOT make changes automatically—report for human confirmation
Output Format
[DIFF CHECK COMPLETE]
Files reviewed: [N]
Issues found: [M]
Critical:
- [file:line] [issue description]
Warnings:
- [file:line] [issue description]
Suggestions:
- [recommendation]
Status: [READY / NEEDS FIXES]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.

