aspiers/code-reviewing
.agents/skills/code-reviewing/SKILL.md
Review code for quality, security, and maintainability. Use after code changes are completed and ready for review.
$ install --global
skillsauthnpx skillsauth add aspiers/ai-config code-reviewingInstall 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 24, 2026, 8:50 PM1.9s1 file scanned
SKILL.md
- name:
- code-reviewing
- description:
- Review code for quality, security, and maintainability. Use after code changes are completed and ready for review.
Code Review
Review code for quality, security, and maintainability.
When to Use This Skill
Use this skill:
- After code changes are completed and ready for review
- Before staging changes for commit
- As a proactive quality check during development
Context
When invoked, examine:
- Current git status:
git status - Current git diff (staged and unstaged changes):
git diff --no-ext-diff HEAD - Current branch:
git branch --show-current - Recent commits:
git log --oneline -40
Review Checklist
Examine all modified files and check:
- NO DUPLICATED CODE! - Extract common logic into reusable functions
- Functions 30 lines or shorter - Break down complex functions
- Well-named functions and variables - Clear, descriptive names
- Simple and readable code - Avoid unnecessary complexity
- Proper error handling - Handle edge cases and failures gracefully
- No exposed secrets or API keys - Use environment variables or config
- Input validation implemented - Validate all external inputs
- Good test coverage - Tests for critical paths
- Performance considerations - No obvious O(n²) or worse patterns
Feedback Organization
Provide feedback organized by priority:
- Critical issues (MUST FIX): Security vulnerabilities, bugs, broken functionality
- Warnings (SHOULD FIX): Code quality, maintainability concerns
- Suggestions (CONSIDER): Improvements that would be nice to have
For each issue, include:
- Specific location (file, line number)
- Description of the problem
- Example of how to fix it
Output
Provide a structured review:
## Critical Issues
- [File:line] Description of issue
- How to fix: ...
## Warnings
- [File:line] Description of concern
- Suggestion: ...
## Suggestions
- [File:line] Nice-to-have improvement
If no issues found: "Code review passed. No issues identified."
Related Skills
aspiers/test-running
development
VerifiedTrustedCommunity
Run tests according to repository guidelines. Use after linting passes, before staging changes.
9SKILL.mdUpdated Apr 17, 2026
aspiers/task-orchestration
development
VerifiedTrustedCommunity
Orchestrate the complete development workflow for implementing sub-tasks from a task list. Use for end-to-end feature implementation with quality controls.
9SKILL.mdUpdated Apr 17, 2026
aspiers/task-implementation
development
VerifiedTrustedCommunity
Implement a single sub-task from a task list. Use when working on feature development with existing task lists.
9SKILL.mdUpdated Apr 17, 2026
aspiers/task-generation
data-ai
VerifiedTrustedCommunity
Generate a detailed task list from a PRP. Use after a PRP is created and ready for implementation planning.
9SKILL.mdUpdated Apr 17, 2026