AgentSkillsCN

soda-review

从四个角度审视分支变更

SKILL.md
--- frontmatter
name: soda-review
description: Review branch changes from four perspectives
user-invocable: true
argument-hint: [focus or base branch]
allowed-tools: Bash(git *), Read, Grep, Glob, AskUserQuestion

Perform a comprehensive code review of the changes on the current branch.

Use English for internal reasoning (thinking). All user-facing output must be in Japanese.

Current Branch Context

!bun ${CLAUDE_PLUGIN_ROOT}/skills/soda-review/scripts/detect-base-branch.ts

The above JSON provides baseBranch, mergeBase, changedFiles, potentialConflicts, and ready-to-use commands.diff / commands.log.

If $ARGUMENTS is not empty, treat it as the review focus or an alternative base branch specification. When an alternative base is specified, re-compute the diff using that base instead of the detected one.

Procedure

  1. •Identify the diff: Use the pre-fetched branch context JSON above. Run commands.diff to get the full diff. If $ARGUMENTS specifies a different base, re-compute the merge-base and diff accordingly. If the JSON contains an error field, present the error to the user and use AskUserQuestion: "Specify a different base branch" / "Cancel review". If the user specifies a different base branch, re-compute the merge-base and diff using that base, then continue from step 2. If the user cancels, end the review. If the diff is empty (no changes between merge-base and HEAD), inform the user and use AskUserQuestion: "Specify a different base branch" / "End review".
  2. •Overview: Summarize the changed files and the overall scope of changes.
  3. •Review: Examine changes from the following perspectives:
    • •Functional correctness (logic bugs, missed edge cases)
    • •Completeness (TODOs, unimplemented parts, missing tests)
    • •Code quality (naming, structure, duplication)
    • •Potential issues (performance, security)
  4. •Report: Present findings ordered by severity.
  5. •Next Steps: After presenting the report, use AskUserQuestion to ask the user what to do next. Adjust the options based on the review outcome:
    • •If issues were found:
      • •"Create a plan to fix the issues" (suggest /soda-plan)
      • •"Note these for later"
    • •If no issues were found:
      • •"Looks good, no action needed"
      • •"Review again with a different focus"

Constraints

  • •Report findings only. Do NOT modify any code.
  • •If a fix is needed, suggest a concrete improvement but do not apply it.