opencode-review
Skill9 starsChanged 8 months agoMITView on GitHub
Code review via OpenCode — review uncommitted changes, branches, or commits
1 other project uses a version of this.
Adopted by
Most recently taken up by
- shyuan/skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- shyuan/skills★ 5same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- add-buddySkill
- brainstormSkill
- campfireSkill
- codex-reviewSkill
- codexSkill
- forgeSkill
- gemini-reviewSkill
- geminiSkill
- leaderboardSkill
- opencodeSkill
- tribunalSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Run the wrapper script via Bash.
- Very specific: line 27
No arguments → review uncommitted changes (--review-target uncommitted)
- Distinctive: line 30
Determine working directory: Must be inside a git repository.
- Distinctive: line 35
Add your own perspective: if you see issues OpenCode missed, or agree with specific points.
- Distinctive: line 65
Always verify we're in a git repo: before running. If not, tell the user.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/opencode-review — Code Review via OpenCode
Get a code review from OpenCode CLI. Reviews uncommitted changes by default, or specify a branch or commit.
How to invoke
Run the wrapper script via Bash. IMPORTANT: OpenCode can take 3-6 minutes depending on the model and task complexity. You MUST set the Bash tool's timeout parameter to 420000 (7 minutes) to prevent Claude Code from killing the process before OpenCode finishes.
bash "${CLAUDE_PLUGIN_ROOT}/scripts/opencode-run.sh" \
--prompt "Additional review instructions (optional)" \
--cwd "/path/to/repo" \
--mode review \
--review-target "uncommitted"Then read the output file and present the review to the user.
Step-by-step workflow
- Determine what to review:
- No arguments → review uncommitted changes (
--review-target uncommitted) - User specifies a branch →
--review-target branch:branch-name - User specifies a commit →
--review-target commit:SHA
- No arguments → review uncommitted changes (
- Determine working directory. Must be inside a git repository.
- Build the prompt. The wrapper automatically fetches the diff and builds a review prompt. If the user provides extra instructions (e.g., "focus on security"), pass them as
--prompt. - Run opencode-run.sh with
--mode reviewvia the Bash tool. - Read the output file using the Read tool.
- Present the review to the user. Frame it as "OpenCode's code review:" with clear sections.
- Add your own perspective if you see issues OpenCode missed, or agree with specific points.
Options
| Flag | Default | Description |
--prompt | (optional) | Extra review instructions |
--cwd | current dir | Working directory (must be a git repo) |
--mode | review | Always review for this skill |
--review-target | uncommitted | What to review |
--timeout | from config (360s) | Max seconds to wait |
--model | from config | Override the model (format: provider/model) |
Review targets
| Target | Flag | Example |
| Uncommitted changes | --review-target uncommitted | /opencode-review |
| Branch diff | --review-target branch:NAME | /opencode-review branch:feature/auth |
| Specific commit | --review-target commit:SHA | /opencode-review commit:abc1234 |
Example invocations
/opencode-review— review all uncommitted changes/opencode-review branch:main— review diff from main to HEAD/opencode-review commit:a1b2c3d— review a specific commit/opencode-review "focus on security and SQL injection"— review with extra instructions
Rules
- Always verify we're in a git repo before running. If not, tell the user.
- If no changes exist, tell the user there's nothing to review instead of sending an empty diff.
- Present both perspectives — show OpenCode's review, then add your own observations.
- Don't auto-apply suggestions — present findings and let the user decide what to fix.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.