allofmeng/code-reviewer
.agents/skills/code-reviewer/SKILL.md
Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.
$ install --global
skillsauthnpx skillsauth add allofmeng/streamline_project code-reviewerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 5, 2026, 1:57 PM26.4s1 file scanned
SKILL.md
- name:
- code-reviewer
Code Reviewer
This skill guides the agent in conducting professional and thorough code reviews for both local development and remote Pull Requests.
Workflow
1. Determine Review Target
- Remote PR: If the user provides a PR number or URL (e.g., "Review PR #123"), target that remote PR.
- Local Changes: If no specific PR is mentioned, or if the user asks to "review my changes", target the current local file system states (staged and unstaged changes).
2. Preparation
For Remote PRs:
- Checkout: Use the GitHub CLI to checkout the PR.
gh pr checkout <PR_NUMBER> - Preflight: Execute the project's standard verification suite to catch automated failures early.
npm run preflight - Context: Read the PR description and any existing comments to understand the goal and history.
For Local Changes:
- Identify Changes:
- Check status:
git status - Read diffs:
git diff(working tree) and/orgit diff --staged(staged).
- Check status:
- Preflight (Optional): If the changes are substantial, ask the user if they want to run
npm run preflightbefore reviewing.
3. In-Depth Analysis
Analyze the code changes based on the following pillars:
- Correctness: Does the code achieve its stated purpose without bugs or logical errors?
- Maintainability: Is the code clean, well-structured, and easy to understand and modify in the future? Consider factors like code clarity, modularity, and adherence to established design patterns.
- Readability: Is the code well-commented (where necessary) and consistently formatted according to our project's coding style guidelines?
- Efficiency: Are there any obvious performance bottlenecks or resource inefficiencies introduced by the changes?
- Security: Are there any potential security vulnerabilities or insecure coding practices?
- Edge Cases and Error Handling: Does the code appropriately handle edge cases and potential errors?
- Testability: Is the new or modified code adequately covered by tests (even if preflight checks pass)? Suggest additional test cases that would improve coverage or robustness.
4. Provide Feedback
Structure
- Summary: A high-level overview of the review.
- Findings:
- Critical: Bugs, security issues, or breaking changes.
- Improvements: Suggestions for better code quality or performance.
- Nitpicks: Formatting or minor style issues (optional).
- Conclusion: Clear recommendation (Approved / Request Changes).
Tone
- Be constructive, professional, and friendly.
- Explain why a change is requested.
- For approvals, acknowledge the specific value of the contribution.
5. Cleanup (Remote PRs only)
- After the review, ask the user if they want to switch back to the default branch (e.g.,
mainormaster).
Related Skills
allofmeng/streamline_project
development
VerifiedTrustedCommunity
--- name: clean-code-reviewer description: Use this agent when reviewing recently written code to identify redundancy, improve cleanliness, suggest refactoring opportunities, and recommend tests based on existing modules and project architecture. color: Blue --- You are an expert code reviewer with a specialized focus on ensuring code cleanliness and eliminating redundancy. Your primary responsibilities include analyzing recently written code for quality, identifying duplicate functionality, s
9SKILL.mdUpdated Apr 15, 2026
allofmeng/.opencode
development
VerifiedTrustedCommunity
--- name: clean-code-reviewer description: Use this agent when reviewing recently written code to identify redundancy, improve cleanliness, suggest refactoring opportunities, and recommend tests based on existing modules and project architecture. compatibility: opencode color: Blue --- You are an expert code reviewer with a specialized focus on ensuring code cleanliness and eliminating redundancy. Your primary responsibilities include analyzing recently written code for quality, identifying du
7SKILL.mdUpdated Apr 15, 2026
allofmeng/.gemini/skills
development
VerifiedTrustedCommunity
--- name: clean-code-reviewer description: Use this agent when reviewing recently written code to identify redundancy, improve cleanliness, suggest refactoring opportunities, and recommend tests based on existing modules and project architecture. color: Blue --- You are an expert code reviewer with a specialized focus on ensuring code cleanliness and eliminating redundancy. Your primary responsibilities include analyzing recently written code for quality, identifying duplicate functionality, s
7SKILL.mdUpdated Apr 15, 2026
allofmeng/implement-design
tools
VerifiedTrustedCommunity
Translates Figma designs into production-ready code with 1:1 visual fidelity. Use when implementing UI from Figma files, when user mentions "implement design", "generate code", "implement component", "build Figma design", provides Figma URLs, or asks to build components matching Figma specs. Requires Figma MCP server connection.
7SKILL.mdUpdated Apr 15, 2026