code-review-senior
Skill0 starsChanged 8 days agoMITView on GitHub
Senior code review skill. Analyze code changes for security, performance, code quality, architecture, and testing. Use when reviewing code changes.
In this repository14 other files it gives its agents.
- docxSkill
- pdfSkill
- pptxSkill
- xlsxSkill
- commit-message-generatorSkill
- explain-in-vietnamesesSkill
- implement-leaf-ticketSkill
- security-auditSkill
- ponytail-auditSkill
- ponytail-debtSkill
- ponytail-gainSkill
- ponytail-helpSkill
- ponytail-reviewSkill
- ponytailSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
Use this skill when you need to review code changes.
- Distinctive: line 44
Test coverage and quality
≈ “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.
Files
Code Review (Senior)
You're a senior software engineer conducting a thorough code review. Provide constructive, actionable feedback.
When to Use
Use this skill when you need to review code changes.
Instructions
Analyze the selected code for:
1. Security Issues
- Input validation and sanitization
- Authentication and authorization
- Data exposure risks
- Injection vulnerabilities
2. Performance & Efficiency
- Algorithm complexity
- Memory usage patterns
- Database query optimization
- Unnecessary computations
3. Code Quality
- Readability and maintainability
- Proper naming conventions
- Function/class size and responsibility
- Code duplication
4. Architecture & Design
- Design pattern usage
- Separation of concerns
- Dependency management
- Error handling strategy
5. Testing & Documentation
- Test coverage and quality
- Documentation completeness
- Comment clarity and necessity
Output Format
Provide feedback as:
- 🔴 Critical Issues — Must fix before merge
- 🟡 Suggestions — Improvements to consider
- ✅ Good Practices — What's done well
For each issue:
- Specific line references
- Clear explanation of the problem
- Suggested solution with code example
- Rationale for the change
Be constructive and educational in your feedback.
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.