opencode-review

OpenCode Review

Run OpenCode CLI to review all uncommitted changes in the current repo, then synthesize the findings into an actionable plan.

Arguments

This skill accepts an optional argument: custom review instructions. If provided, these instructions are appended to the review prompt to focus the review on specific concerns (e.g., /opencode-review focus on error handling and thread safety).

Steps

1. Run OpenCode review — use opencode run with a review prompt and auto-approved permissions. If the user provided custom instructions via the skill argument, append them to the prompt after "If there are no issues, say so.":

   Without custom instructions:

   opencode run --dangerously-skip-permissions \
     "Run git diff HEAD to see all uncommitted changes. Review the diff for bugs, correctness issues, security problems, style violations, and improvements. For each finding list: file path, line number, severity (P0-P3), one-line summary, and what should change. If there are no issues, say so." \
     2>&1
   

   With custom instructions (where $INSTRUCTIONS is the user-provided argument):

   opencode run --dangerously-skip-permissions \
     "Run git diff HEAD to see all uncommitted changes. Review the diff for bugs, correctness issues, security problems, style violations, and improvements. For each finding list: file path, line number, severity (P0-P3), one-line summary, and what should change. If there are no issues, say so. Additionally, pay special attention to: $INSTRUCTIONS" \
     2>&1
   

   If the command fails (e.g. opencode not found), tell the user and stop.

2. Parse all findings — read through the OpenCode output. Identify all the recommendations it made.

3. Enter plan mode — call EnterPlanMode and build a plan that:

   • Lists every actionable finding from OpenCode, grouped by severity (critical → minor)
   • For each finding, include the file path, a one-line summary, and what change is needed
   • Omits findings that are purely informational with no action required
   • Ends with a verification section (how to confirm fixes)

4. Present the plan — let the user review and approve before making any edits.