install
source · Clone the upstream repo
git clone https://github.com/openclaw/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/brunoscardoso/plan-flow/review-code" ~/.claude/skills/openclaw-skills-review-code && rm -rf "$T"
OpenClaw · Install into ~/.openclaw/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/brunoscardoso/plan-flow/review-code" ~/.openclaw/skills/openclaw-skills-review-code && rm -rf "$T"
manifest:
skills/brunoscardoso/plan-flow/review-code/SKILL.mdsource content
Review Code
Review local uncommitted changes in the repository.
What It Does
- Gets git diff of changes (staged, unstaged, or all)
- Identifies changed files and their patterns
- Finds similar implementations in the codebase
- Reviews against project patterns and rules
- Provides findings with severity and fix suggestions
- Generates a review document
Usage
/review-code [path] [scope]
Arguments:
(optional): Specific file or directory to reviewpath
(optional):scope
,staged
, orunstaged
(default: all)all
Output
Creates:
flow/reviewed-code/review_<scope>.md
Review Categories
| Severity | Description | Action Required |
|---|---|---|
| Critical | Security issues, major bugs | Must fix before commit |
| Major | Significant problems | Should fix |
| Minor | Code quality issues | Consider fixing |
| Suggestion | Improvements | Optional |
Review Document Structure
# Code Review: [Scope] ## Review Information | Field | Value | |-------|-------| | Date | YYYY-MM-DD | | Files Reviewed | N | | Scope | all/staged/unstaged | ## Changed Files | File | Status | Lines Changed | |------|--------|---------------| | path/to/file | modified | +10/-5 | ## Findings ### Finding 1: [Name] | Field | Value | |-------|-------| | File | path/to/file | | Line | 42 | | Severity | Major | | Fix Complexity | 3/10 | **Description**: What's wrong **Suggested Fix**: How to fix it ## Commit Readiness | Status | Ready to Commit / Needs Changes |
Example
/review-code
Scoped review:
/review-code src/components staged
What It Checks
- Pattern consistency with existing codebase
- Error handling completeness
- Type safety (for TypeScript)
- Security concerns (hardcoded secrets, injection risks)
- Performance considerations
- Code organization and naming
Next Command
After fixing issues, commit your changes or run
/review-pr after creating a PR.