Code review analysis
Skill ulpi-io/plugin-marketplace/plugins/aj-geddes/skills/code-review-analysis
A curated collection of 7,800+ agent skills for Claude Desktop, sourced from skills.sh
npx -y skills add ulpi-io/plugin-marketplace --skill code-review-analysisAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Perform comprehensive code reviews with best practices, security checks, and constructive feedback. Use when reviewing pull requests, analyzing code quality, checking for security vulnerabilities, or providing code improvement suggestions.
SKILL.md
2.2 KB, as published. Nobody here has run it
Code Review Analysis
Table of Contents
Overview
Systematic code review process covering code quality, security, performance, maintainability, and best practices following industry standards.
When to Use
- Reviewing pull requests and merge requests
- Analyzing code quality before merging
- Identifying security vulnerabilities
- Providing constructive feedback to developers
- Ensuring coding standards compliance
- Mentoring through code review
Quick Start
Minimal working example:
# Check the changes
git diff main...feature-branch
# Review file changes
git diff --stat main...feature-branch
# Check commit history
git log main...feature-branch --oneline
Reference Guides
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| Initial Assessment | Initial Assessment |
| Code Quality Analysis | Code Quality Analysis |
| Security Review | Security Review |
| Performance Review | Performance Review |
| Testing Review | Testing Review |
| Best Practices | Best Practices |
Best Practices
✅ DO
- Be constructive and respectful
- Explain the "why" behind suggestions
- Provide code examples
- Ask questions if unclear
- Acknowledge good practices
- Focus on important issues
- Consider the context
- Offer to pair program on complex issues
❌ DON'T
- Be overly critical or personal
- Nitpick minor style issues (use automated tools)
- Block on subjective preferences
- Review too many changes at once (>400 lines)
- Forget to check tests
- Ignore security implications
- Rush the review