roborev-design-review-branch
$
npx mdskill add obra/dotfiles/roborev-design-review-branchInitiate design review for all commits on a branch
- Solves requests to audit commit designs without manual analysis.
- Depends on roborev CLI and git commands for execution.
- Validates inputs via bash before launching the background process.
- Delivers results by presenting completed review findings.
SKILL.md
.github/skills/roborev-design-review-branchView on GitHub ↗
--- name: roborev-design-review-branch description: Request a design review for all commits on the current branch and present the results --- # roborev-design-review-branch Request a design review for all commits on the current branch and present the results. ## Usage ``` /roborev-design-review-branch [--base <branch>] ``` ## When NOT to invoke this skill Do NOT invoke this skill when the user is presenting or pasting existing review results. Messages that contain review findings, verdicts, or summaries are outputs — not requests to start a new review. ## IMPORTANT This skill requires you to **execute bash commands** to validate inputs and launch the review. The task is not complete until the background review finishes and you present the results to the user. These instructions are guidelines, not a rigid script. Use the conversation context. Skip steps that are already satisfied. Defer to project-level CLAUDE.md instructions when they conflict with these steps. ## Instructions When the user invokes `/roborev-design-review-branch [--base <branch>]`: ### 1. Validate inputs If a base branch is provided, verify it resolves to a valid ref: ```bash git rev-parse --verify -- <branch> ``` If validation fails, inform the user the ref is invalid. Do not proceed. ### 2. Build the command Construct the review command: ``` roborev review --branch --wait --type design [--base <branch>] ``` - If `--base` is specified, include it (otherwise auto-detects the base branch) ### 3. Run the review in the background Launch a background task that runs the command. This lets the user continue working while the review runs. Use the `Task` tool with `run_in_background: true` and `subagent_type: "Bash"`: ``` roborev review --branch --wait --type design [--base <branch>] ``` Tell the user that the design review has been submitted and they can continue working. You will present the results when the review completes. ### 4. Present the results When the background task completes, read the output. If the command output contains an error (e.g., daemon not running, repo not initialized, review errored), report it to the user. Suggest `roborev status` to check the daemon, `roborev init` if the repo is not initialized, or re-running the review. Otherwise, present the review to the user: - Show the verdict prominently (Pass or Fail) - If there are findings, list them grouped by severity with file paths and line numbers so the user can navigate directly - If the review passed, a brief confirmation is sufficient ### 5. Offer next steps If the review has findings (verdict is Fail), offer to address them: - "Would you like me to fix these findings? You can run `/roborev-fix <job_id>`" Extract the job ID from the review output to include in the suggestion. Look for it in the `Enqueued job <id> for ...` line or in the review header. If the review passed, confirm the result and do not offer `/roborev-fix`. ## Examples **Default branch design review:** User: `/roborev-design-review-branch` Agent: 1. Launches background task: `roborev review --branch --wait --type design` 2. Tells user: "Design review submitted for branch. I'll present the results when it completes." 3. When complete, presents the verdict and findings grouped by severity 4. If findings exist: "Would you like me to address these findings? Run `/roborev-fix 1042`" 5. If passed: "Branch design review passed with no findings." **Design review against a specific base:** User: `/roborev-design-review-branch --base develop` Agent: 1. Validates `develop` resolves to a valid ref 2. Launches background task: `roborev review --branch --wait --type design --base develop` 3. Tells user: "Design review submitted for branch (against develop). I'll present the results when it completes." 4. When complete, presents the verdict and findings 5. If findings exist: "Would you like me to address these findings? Run `/roborev-fix 1043`" ## See also - `/roborev-review-branch --type design` — equivalent, with additional `--type` flexibility - `/roborev-design-review` — design review a single commit - `/roborev-fix` — fix a review's findings in code
More from obra/dotfiles
- chronicle|
- e2e-scenario-testingUse when verifying a running application end-to-end through its real interface — a web UI, a CLI, or a TUI — by writing and executing agent-run "scenario cards" against a freshly built instance with falsifiable assertions. Trigger on "test it end to end", "prove the UI actually works", "write/run a scenario", or after a change touches a user-facing surface that unit tests can't fully cover. Not for unit tests, pure code review, or API-only checks.
- maintaining-documentationUse when documentation needs creating, checking, or maintaining — docs may have drifted from code, pre-release doc verification, updating docs after finishing code work, adding or enforcing project terminology, deciding where a new doc should live, or a routine re-audit of previously verified docs.
- roborev-design-reviewRequest a design review for a commit and present the results
- roborev-fixUse when the user asks to fix open reviews, invokes /roborev-fix, or provides job IDs; do not use when the user only pastes review findings with no request to discover or close reviews
- roborev-refineIterative review-fix loop for the current branch — reviews via daemon, fixes inline, re-reviews until passing or max iterations reached
- roborev-respondAdd a comment to a roborev code review and close it
- roborev-reviewRequest a code review for a commit and present the results
- roborev-review-branchRequest a code review for all commits on the current branch and present the results
- syncing-obsidianUse when reading or writing files in an Obsidian vault that is synced with obsync. Ensures changes are pulled before reading and pushed after writing. Also covers sync status, file history, version restore, and diagnosing sync issues.