code-review · cloudshipai — Claude Code skill: what it does, how to install
code-review audits code and pull requests for security flaws, performance bugs, and testing gaps. Helpful when reviewing branches before merging into production.
Apache-2.0 1 installs ★ 431 updated 2026-01-27
npx skills add cloudshipai/station --skill code-review -a claude-codeWhat code-review does
The skill organizes structured code reviews across five specific evaluation areas: functionality with error handling, code clarity, security vulnerabilities, performance bottlenecks, and test coverage. To inspect codebases directly, the agent uses read_file, grep, glob, and bash.
Every detected issue comes with exact file coordinates, line numbers, and a severity rating from Low to Critical. Instead of vague feedback, the review provides actionable guidance and sample code blocks showing before-and-after fixes.
Because the skill relies on bash and file discovery tools, environments with restricted shell execution will limit its ability to inspect diffs and run repository searches.
What it helps with
- spot security flaws like SQL injections and hardcoded secrets
- detect performance bottlenecks including N+1 query patterns
- evaluate test coverage across critical edge cases
- catch duplicate logic and unclear naming before merging
Example prompts for the agent
- Run a code review on the latest pull request diff
- Check
src/api/users.gofor security vulnerabilities and injection risks - Audit this branch for performance issues and edge cases
How to install code-review
1Skills CLI (Vercel)
npx skills add cloudshipai/station --skill code-review -a claude-code2Manually: put the files in place
~/.claude/skills/code-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/code-review/
1Skills CLI (Vercel)
npx skills add cloudshipai/station --skill code-review -a codex2Manually: put the files in place
.agents/skills/code-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cloudshipai/station --skill code-review -a cursor2Manually: put the files in place
.cursor/skills/code-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cloudshipai/station environments/default/skills/user/code-review2Manually: put the files in place
.github/skills/code-review/SKILL.md1Skills CLI (Vercel)
npx skills add cloudshipai/station --skill code-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/cloudshipai/station --path environments/default/skills/user/code-reviewManually: put the files in place
.devin/skills/code-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cloudshipai/station --skill code-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about code-review
How to install code-review in Claude Code?
Add the skill by running npx skills add cloudshipai/station --skill code-review -a claude-code. You can also place the skill file directly into ~/.claude/skills/code-review/SKILL.md.
What areas does this code review skill inspect?
The checklist covers logic and edge cases, naming and structure, vulnerabilities like XSS and SQL injection, resource usage with N+1 queries, and test coverage.
How are review findings structured?
Each issue lists the file and line number, a severity tier from Low to Critical, an explanation of the defect, and a code snippet showing the suggested resolution.
Source text
SKILL.md · Apache-2.0
--- name: code-review description: Systematic code review process with focus on quality, security, and best practices allowed-tools: - read_file - grep - glob - bash triggers: - review - code quality - pull request --- # Code Review Skill ## When to Use - User asks for code review or feedback - Reviewing a pull request or diff - Analyzing code quality or security ## Review Checklist ### 1. Functionality - [ ] Does the code do what it's supposed to? - [ ] Are edge cases handled? - [ ] Is error handling appropriate? ### 2. Code Quality - [ ] Is the code readable and maintainable? - [ ] Are functions and variables named clearly? - [ ] Is there unnecessary duplication? - [ ] Are comments helpful and accurate? ### 3. Security - [ ] Input validation present? - [ ] No hardcoded secrets? - [ ] SQL injection prevention? - [ ] XSS prevention? ### 4. Performance - [ ] Efficient algorithms used? - [ ] No N+1 query problems? - [ ] Resources properly managed? ### 5. Testing - [ ] Tests cover main functionality? - [ ] Edge cases tested? - [ ] Tests are readable? ## Output Format For each finding, provide: 1. **Location**: File and line number 2. **Severity**: Critical / High / Medium / Low 3. **Issue**: Clear description of the problem 4. **Suggestion**: How to fix it 5. **Example**: Code snippet showing the fix (if applicable) ## Example Review Comment **Location**: `src/api/users.go:42` **Severity**: High **Issue**: SQL query built using string concatenation **Suggestion**: Use parameterized queries to prevent SQL injection **Example**: ```go // Before (vulnerable) query := "SELECT * FROM users WHERE id = " + userID // After (safe) query := "SELECT * FROM users WHERE id = ?" db.Query(query, userID) ```
© cloudshipai · Apache-2.0 · cloudshipai/station
Similar skills
All skills for Code review and refactoring →code-review by other authors comes first.