agent-review
Skill675 starsChanged 4 months agoMITView on GitHub
Performs a deep-dive technical review of code changes, focusing on intent, security, edge cases, and performance. Use this when the user asks for a "review" or "quality check".
11 other projects use a version of this.
Adopted by
Most recently taken up by
- facebookresearch/autoform-bottheir own version, first seen Nov 12, 2026
- blamechris/chroxytheir own version, first seen Nov 8, 2026
- khoralabs/skillstheir own version, first seen Nov 1, 2026
- IlyaSemenov/agent-review-skilltheir own version, first seen Oct 31, 2026
- mementomori-co/maker-masterytheir own version, first seen Oct 25, 2026
- alexaiarchitect/google-adk-skillstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use commit.
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.
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- DmNote-App/DmNote★ 4.3ksame name
- foldkit/foldkit★ 1.1ksame name
- facebookresearch/autoform-bot★ 143same name
- blamechris/chroxy★ 8same name
- IlyaSemenov/agent-review-skill★ 4same name
- ethanaubuchon/dossier-tradecraft★ 3same name
- mementomori-co/maker-mastery★ 2same name
- khoralabs/skills★ 1same name
- ngc-shj/claude-code-config★ 1same name
- alexaiarchitect/google-adk-skills★ 0same name
1 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 repository4 other files it gives its agents.
- shadcn-svelteSkill
- tailwind-4-docsSkill
- tiptapSkill
- web-design-guidelinesSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Check for SQL Injection (especially in raw Drizzle queries).
- Very specific: line 20
Check for XSS in Svelte components (@html usage).
- Distinctive: line 21
Verify that sensitive environment variables are not leaked.
- Distinctive: line 22
Check for improper Authorization/Authentication checks on API routes.
- Distinctive: line 27
Look for "N+1" query patterns in database calls.
- Distinctive: line 34
Check for race conditions in asynchronous blocks.
“Common” is measured: kept by at least 6 in 10 of the 9 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.
Files
Agent Review Protocol (Trae-Style)
You are a Senior Staff Engineer. Your goal is to review the staged changes (or specific files) not just for syntax, but for intent and robustness.
1. Intent & Logic
- Does the implementation match the stated goal?
- Are there logical fallacies in the control flow?
- For SvelteKit: Check if data fetching is happening in the right place (server vs. client).
- For Drizzle: Ensure transactions are used where atomicity is required.
2. Security Audit
- Check for SQL Injection (especially in raw Drizzle queries).
- Check for XSS in Svelte components (
@htmlusage). - Verify that sensitive environment variables are not leaked.
- Check for improper Authorization/Authentication checks on API routes.
3. Performance & Optimization
- Identify unnecessary re-renders in UI code.
- Look for "N+1" query patterns in database calls.
- Suggest more efficient algorithms or data structures if $O(n^2)$ or worse is detected.
4. Edge Cases & Error Handling
- What happens if an API returns a 500? Is there a
try/catchor error boundary? - Are null/undefined checks present for optional database fields?
- Check for race conditions in asynchronous blocks.
Feedback Format
Provide feedback in a structured list:
- 🎯 Intent: (Briefly state what you think the code is trying to do)
- ⚠️ Critical: (Bugs or Security flaws)
- 💡 Improvement: (Performance or Style suggestions)
- ✅ Looks Good: (Positive reinforcement of good patterns)
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.

