premerge-review
Skill3 starsChanged 54 days agoNo licenceView on GitHub
Defect-oriented pre-merge code review — first runs the branch through a gauntlet of mechanical checks (tests, lint, harness invariants, test-case bridge, mutation on the diff), then analyzes the diff against main at a depth calibrated on criticality, and produces a structured report with a GO/NO-GO verdict. A red gauntlet stops the review: no point hand-reading a diff that is about to change. Use SYSTEMATICALLY when the user asks for a "code review", "review my branch", "check my diff before merge", "is my PR ready", "review what I did", or before any merge inside an agentic pipeline (pre-merge checkpoint). Covers four angles — bugs/regressions, security, ADR/architecture compliance, debt/readability. Not to be confused with code-assimilation-quiz (developer learning, not defect hunting) or ai-code-remediation (cold audit of a whole codebase, not of a diff).
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-code-remediationSkill
- behavior-driven-testingSkill
- clarify-with-choicesSkill
- code-assimilation-quizSkill
- codebase-cartographerSkill
- codebase-harnessSkill
- ddd-advisorSkill
- plan-driven-devSkill
- product-strategySkill
- systematic-debuggingSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 9 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
3
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 an estimate: at least 1 in 5 of the 350,495 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.
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.