geeksfino/code-review
examples/skills/code-review/SKILL.md
Reviews code for quality, best practices, and potential issues. Use when asked to review, audit, or check code for problems.
$ install --global
skillsauthnpx skillsauth add geeksfino/openskills code-reviewInstall 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 4, 2026, 11:19 PM7.3s1 file scanned
SKILL.md
- name:
- code-review
- description:
- Reviews code for quality, best practices, and potential issues. Use when asked to review, audit, or check code for problems.
- allowed-tools:
- Read, Grep, Glob, LS
- context:
- fork
- agent:
- Explore
Code Review Skill
Perform thorough code reviews following this methodology.
Review Checklist
1. Correctness
- Does the code do what it's supposed to do?
- Are there any logic errors?
- Are edge cases handled?
2. Security
- Input validation and sanitization
- Authentication and authorization
- Sensitive data handling
- SQL injection, XSS, and other vulnerabilities
3. Performance
- Algorithm complexity
- Unnecessary computations
- Memory leaks or inefficient memory usage
- Database query optimization
4. Maintainability
- Code readability and clarity
- Appropriate naming conventions
- Single responsibility principle
- DRY (Don't Repeat Yourself)
5. Testing
- Test coverage
- Edge case testing
- Integration tests where appropriate
Output Format
Structure your review as:
## Summary
[One paragraph overview]
## Critical Issues
[Must fix before merge]
## Suggestions
[Nice to have improvements]
## Positive Observations
[What's done well]
Guidelines
- Be constructive, not critical
- Explain why something is an issue
- Suggest specific fixes when possible
- Acknowledge good patterns and practices
Related Skills
geeksfino/skill-creator
tools
VerifiedTrustedCommunity
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
45SKILL.mdUpdated Apr 4, 2026
geeksfino/fork-test
testing
VerifiedTrustedCommunity
Minimal skill for testing context fork behavior. Do not use in production.
45SKILL.mdUpdated Apr 4, 2026
geeksfino/explaining-code
development
VerifiedTrustedCommunity
Explains code clearly and thoroughly. Use when asked to explain, clarify, or teach about code snippets, functions, or concepts.
45SKILL.mdUpdated Apr 4, 2026
geeksfino/openskills-skill-authoring
data-ai
VerifiedTrustedCommunity
Create and refine OpenSkills-compatible skills (SKILL.md + optional resources) with strong metadata, clear activation triggers, and reliable execution guidance.
45SKILL.mdUpdated Apr 4, 2026