aiskillstore/code-review
skills/21pounder/code-review/SKILL.md
Use this skill when user asks to "review code", "check for issues", "analyze code quality", "find bugs", or wants feedback on code implementation.
$ install --global
skillsauthnpx skillsauth add aiskillstore/marketplace 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: Mar 28, 2026, 12:00 PM35.7s2 files scanned
SKILL.md
- name:
- code-review
- description:
- Use this skill when user asks to "review code", "check for issues", "analyze code quality", "find bugs", or wants feedback on code implementation.
- version:
- 1.0.0
- allowed-tools:
- [Read, Glob, Grep]
Code Review
Perform thorough code review analyzing quality, potential bugs, security issues, and suggesting improvements.
Parameters
{
"type": "object",
"properties": {
"target": {
"type": "string",
"description": "File path, directory, or glob pattern to review"
},
"focus": {
"type": "string",
"enum": ["general", "security", "performance", "maintainability"],
"description": "Primary focus area",
"default": "general"
}
},
"required": ["target"]
}
When to Use
- User asks to "review" or "check" code
- User wants to find bugs or issues
- User asks about code quality
- User wants security analysis
- User asks for improvement suggestions
Methodology
Phase 1: Context Gathering
- Read the target files
- Understand the codebase structure
- Identify the programming language and framework
- Check for related tests and documentation
Phase 2: Analysis
- Logic Review: Check for bugs and edge cases
- Security Scan: Look for vulnerabilities (injection, auth issues, etc.)
- Performance Check: Identify bottlenecks and inefficiencies
- Style Review: Check consistency and best practices
Phase 3: Prioritization
- Categorize issues by severity (Critical, High, Medium, Low)
- Focus on actionable feedback
- Provide concrete examples
Phase 4: Output
Provide structured review with:
- Summary of findings
- Issues list with severity and line numbers
- Specific improvement suggestions
- Code examples where helpful
Guidelines
- Be constructive, not just critical
- Provide specific line references
- Explain WHY something is an issue
- Suggest concrete fixes, not just problems
- Acknowledge good patterns when found
- Consider the project's existing style
Examples
Example 1: File Review
User Input: "Review src/auth.ts for security issues"
Expected Behavior:
- Read the file and understand authentication flow
- Check for common security issues (SQL injection, XSS, weak crypto)
- Verify input validation and sanitization
- Check for proper error handling
- Provide prioritized list of findings with fixes
Example 2: Directory Review
User Input: "帮我 review 一下 src/utils/ 目录的代码质量"
Expected Behavior:
- 列出并读取目录中的所有文件
- 分析代码结构、命名、错误处理
- 检查是否有重复代码或可抽象的模式
- 用中文输出详细的 review 报告
- 按严重程度排序问题列表
Related Skills
aiskillstore/hig-components-content
development
VerifiedTrustedCommunity
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/helpdesk-automation
tools
VerifiedTrustedCommunity
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/haskell-pro
testing
VerifiedTrustedCommunity
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/graphql
tools
VerifiedTrustedCommunity
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.
244SKILL.mdUpdated Apr 10, 2026