بنقرة واحدة
roborev-design-review-branch
Request a design review for all commits on the current branch and present the results
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Request a design review for all commits on the current branch and present the results
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user asks to fix open failing 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
Allows you to view the user's screen as well as several hours of history. Use when the user makes a reference to their recent work, for which it'd be helpful to see the screen. This skill MUST be used whenever you need to resolve ambiguity in a user request, where the user hasn't specified enough context to do the task. Examples include disambiguating the specific user/app/document/error the user is referring to. You must also use this skill if the user asks about any question regarding Chronicle or asks what you can see from the screen.
Use when the user asks to fix open failing 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
Request a design review for all commits on the current branch and present the results
Request a design review for a commit and present the results
Iterative review-fix loop for the current branch — reviews via daemon, fixes inline, re-reviews until passing or max iterations reached
| name | roborev-design-review-branch |
| description | Request a design review for all commits on the current branch and present the results |
Request a design review for all commits on the current branch and present the results.
$roborev-design-review-branch [--base <branch>] [--panel <name>|none]
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.
This skill requires you to execute bash commands to validate inputs and run the review. The task is not complete until the 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.
When the user invokes $roborev-design-review-branch [--base <branch>] [--panel <name>|none]:
If a base branch is provided, verify it resolves to a valid ref:
git rev-parse --verify -- <branch>
If validation fails, inform the user the ref is invalid. Do not proceed.
Construct and execute the review command:
roborev review --branch --wait --type design [--base <branch>] [--panel <name>|none]
--base is specified, include it (otherwise auto-detects the base branch)--panel <name> is specified, include it (fans out to the named config panel); --panel none forces a single-agent reviewThe --wait flag blocks until the review completes.
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:
If you pass --panel <name>, or a default_panel is configured for explicit
reviews, the review fans out to a panel of reviewers. In that case the
Enqueued job <id> is the synthesis (parent) job that aggregates them, and
its verdict and findings are the synthesized result across the whole panel.
Present that synthesized verdict/findings, and offer fix on that parent id —
never an individual reviewer. roborev show prints a one-line reviewers summary
(e.g. 3 reviewers: bug P, security F) for a synthesis job. --panel none
forces a single-agent review, and automatic post-commit hook reviews stay
single-agent regardless of default_panel.
If the review has findings (verdict is Fail), offer to address them:
$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. For a panel review this id is the synthesis parent.
If the review passed, confirm the result and do not offer $roborev-fix.
Default branch design review:
User: $roborev-design-review-branch
Agent:
roborev review --branch --wait --type design$roborev-fix 1042"Design review against a specific base:
User: $roborev-design-review-branch --base develop
Agent:
git rev-parse --verify -- developroborev review --branch --wait --type design --base develop$roborev-fix 1043"$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