본문으로 건너뛰기
cccskills
무료GitHub에 공개

roborev-respond

Add a comment to a roborev code review and close it

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md2.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

roborev-respond

Record a comment on a roborev code review and close it.

Usage

/roborev-respond <job_id> [message]

IMPORTANT

This skill requires you to execute bash commands to record the comment and close the review. The task is not complete until you run both commands and see confirmation output.

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-respond <job_id> [message]:

1. Validate input

If no job_id is provided, inform the user that a job ID is required. Suggest roborev status or roborev fix --list to find job IDs. Discovery surfaces synthesis parents (and non-panel reviews), never individual panel members, so the job ID you comment on and close is the parent.

If a job_id is provided, inspect it before closing:

roborev show --job <job_id> --json

If job.panel_role is "member", do not comment on or close that job. Resolve the synthesis parent for the same job.panel_run_uuid if it is already known from the conversation or discovery output; otherwise ask the user for the synthesis parent ID. Only continue once the resolved job ID is a synthesis parent or a non-panel review.

2. Record the comment and close the review

If a message is provided, immediately execute:

roborev comment --job <resolved_job_id> "<message>" && roborev close <resolved_job_id>

If the message contains quotes or special characters, escape them properly in the bash command.

If no message is provided, ask the user what they'd like to say, then execute the commands with their comment.

3. Verify success

Both commands will output confirmation. If either fails, report the error to the user. Common causes:

  • The daemon is not running
  • The job ID does not exist
  • The repo is not initialized (suggest roborev init)
  • The review is already closed (not an error, but worth noting to the user)

The comment is recorded in roborev's database and the review is closed. View results with roborev show.

Examples

With message provided:

User: /roborev-respond 1019 Fixed all issues

Agent action:

roborev comment --job 1019 "Fixed all issues" && roborev close 1019

Then confirm: "Comment recorded and review #1019 closed."


Without message:

User: /roborev-respond 1019

Agent: "What would you like to say about review #1019?"

User: "The null check was a false positive"

Agent action:

roborev comment --job 1019 "The null check was a false positive" && roborev close 1019

Then confirm: "Comment recorded and review #1019 closed."

See also

  • /roborev-fix — fix a review's findings in code, then comment and close it

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

chronicle

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

obra/dotfiles1162026년 10월 13일 업데이트

Use 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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

obra/dotfiles1162026년 10월 13일 업데이트

Use 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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

obra/dotfiles1162026년 10월 13일 업데이트

mcp-cli

무료

Use MCP servers on-demand via the mcp CLI tool - discover tools, resources, and prompts without polluting context with pre-loaded MCP integrations

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

obra/dotfiles1162026년 10월 13일 업데이트

Request a design review for a commit and present the results

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

obra/dotfiles1162026년 10월 13일 업데이트

Request a design review for all commits on the current branch and present the results

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

obra/dotfiles1162026년 10월 13일 업데이트

obra의 스킬 모두 보기

이 스킬의 문제 신고