self-review
Skill1 starsChanged 14 days agoMITView on GitHub
Phase 6. Reviews the full branch diff against requirements, security, data and UI checklists, and fixes findings before the MR. Use after run-checks prints ALL PASS.
53 other projects use a version of this.
Adopted by
Most recently taken up by
- gilsmt/skillstheir own version, first seen Nov 16, 2026
- Fractera/web4-node-starter-kittheir own version, first seen Nov 15, 2026
- crbnos/carbontheir own version, first seen Nov 15, 2026
- Fractera/Agent-Engineering-Infrastructuretheir own version, first seen Nov 8, 2026
- Fractera/Agentic-Engineering-Infrastructuretheir own version, first seen Nov 8, 2026
- plannotator/dev-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use latex-formatting, novelty-assessment and 10 more.
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.
lingzhi227Skilllatex-formatting
Handle LaTeX formatting, templates, and styling for academic papers. Set up conference templates (ICML, ICLR, NeurIPS, AAAI, ACL), fix formatting issues, manage packages, and ensure venue-specific compliance. Use when the user needs to set up a paper template, fix LaTeX formatting, or prepare for submission.
Also in 4 projects that use this
lingzhi227Skillnovelty-assessment
Assess research idea novelty through systematic literature search. Multi-round search-evaluate loops with harsh critic persona. Binary novel/not-novel decision with justification. Use before committing to a research direction.
Also in 4 projects that use this
michaelboedingSkillslide-generation
Use this skill to create presentation slides from structured content. Triggers: "create slides", "generate presentation", "make powerpoint", "create pptx", "build slides", "presentation from content", "slide deck", "slides for" Outputs: PPTX files, Markdown slides, or HTML presentations. Used by: pitch-deck-agent, market-researcher-agent, and other agents needing slides.
Also in 4 projects that use this
juanlurgSkillpaper-to-code
Reads a research paper and generates an implementation notebook with equations, code, and a toy example. Use when the user wants to implement a paper, convert a paper to code, or reproduce a paper's algorithm.
Also in 4 projects that use this
OpenAISkillidea-generation
Use when triaging public-equity idea candidates. Do not use for final trade recommendations, pitches, memos, or models.
Also in 3 projects that use this
sunnyclinches44Skillexplain
Explains code using real-world analogies and ASCII diagrams
Also in 5 projects that use this
- +6 more from lingzhi227
Other versions53 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 53
- huggingface/diffusers★ 35ksame name
- zulip/zulip★ 26ksame name
- flashinfer-ai/flashinfer★ 6.9ksame name
- unkeyed/unkey★ 5.5ksame name
- crbnos/carbon★ 2.8ksame name
- verl-project/verl-omni★ 1.5ksame name
- K9i-0/ccpocket★ 1.1ksame name
- anyproto/anytype-swift★ 525same name
- hegeldev/hegel-rust★ 400same name
- lingzhi227/agent-research-skills★ 350same name
43 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 repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/00-ticket-workflow.mdcCursor rule
- .cursor/rules/10-general-standards.mdcCursor rule
- .cursor/rules/20-backend-standards.mdcCursor rule
- .cursor/rules/30-frontend-standards.mdcCursor rule
- .cursor/rules/40-database-standards.mdcCursor rule
- .cursor/rules/50-testing-standards.mdcCursor rule
- backend-implementSkill
- chatSkill
- codebase-exploreSkill
- db-migrationSkill
- frontend-implementSkill
- gitlab-mrSkill
- implementation-planSkill
- jira-createSkill
- mr-feedbackSkill
- mr-reviewSkill
- quick-fixSkill
- run-checksSkill
- ticket-intakeSkill
- ticket-qaSkill
- write-testsSkill
The file
Files
Self-review (phase 6)
Steps
MB=$(git merge-base origin/main HEAD), thengit diff $MB --stat. Review ONE file at a time:git diff $MB -- <file>.- For each file, go through the checklist below. Write each finding in PROGRESS.md under
"Self-review" as
file:line: problem → fix. - Fix all findings. Then run /run-checks again until
ALL PASS.
Checklist
Requirements and scope
- Every AC in REQUIREMENTS.md has code AND a test, and each test's red line is in PROGRESS.md
- Only files listed in PLAN.md changed; no unrelated formatting or refactors Security
- Every new endpoint requires auth and checks ownership/role in the service
Create/Updateschemas accept no server-owned fields (id, owner id,role,is_admin, timestamps)- All input validated by schema constraints; no SQL built from strings
- No secrets, tokens or personal data in code, logs or responses
- No user data rendered as HTML (
dangerouslySetInnerHTML); external data validated before use Data and performance - No query inside a loop (N+1); new filter/sort columns have indexes
- No unbounded query or loop: lists are paginated
- A new cache states its key (including the user or tenant) and how it goes stale
- Multi-write operations are in one transaction
- Migration downgrade reverses upgrade; no ES mapping/index changes Errors
- No swallowed exceptions; errors map to the correct status code
- The UI shows a helpful message for every error the API can return Frontend
- Loading / empty / error / success states exist
- Labels and
aria-labels present; noany; list keys are ids Quality - Files ≤ 200 lines, functions ≤ 40 lines, nesting ≤ 3
- Clear names; no duplicated logic (search for similar helpers)
- No branch bolted onto an unrelated flow; feature logic stays out of shared modules
- No code left unused by this change (list it and ask before deleting); no abstraction with one user
- No generic names (
data,result,temp), boolean flag parameters or nested ternaries - Code you deleted but didn't write: you found out why it existed first (
git log -Lor blame) - No debug code, commented-out code, or TODO without a ticket key
Done when
- Every checklist item checked for every file
- All findings fixed and listed in PROGRESS.md
ALL PASSshown in this chat after the 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.

