メニュー
After a task's PR is created, offer to close the task on the configured board and reindex it. Use when the user says a PR is up or asks to close or finish a task.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | reviewer_finish-task |
| description | After a task's PR is created, offer to close the task on the configured board and reindex it. Use when the user says a PR is up or asks to close or finish a task. |
Reply in Russian. The server appends the PR link idempotently, completes the selected generic target, and adds a clickable task link to the PR body; clients never send credentials.
task_board from .review.yml, otherwise get_board_config(). Use only
type, project, create_target, done_target, and options. If no board is resolved,
report a board-less no-op.key_pattern on the current branch, newest briefs file, or
gh pr view --json title,body; otherwise ask. Resolve the PR URL with gh pr view --json url -q .url (or ask). Missing key or URL is a no-op.get_board_targets(board_type=<type>, project=<project>, provider_options=<task_board.options or {}>). Select done_target from targets with a done
purpose. For each option with required_for containing finish, resolve its value from
choices; if required metadata is missing, ask instead of guessing.finish_task(key=<key>, pr_url=<url>, note=<note or null>, board_type=<type>,
target=<done_target or null>, provider_options=<task_board.options or {}>)
status == "error", report the reason in Russian and stop.sync_board(board=<project or null>, board_type=<type>, provider_options=<task_board.options or {}>), then report the write and sync result. When
already_closed is true, state that no duplicate PR link was added. Report task_link_added:
when false, relay the warning verbatim — the board write still succeeded.All reads are fail-open; the explicitly confirmed finish_task call is the only write.
Gather disciplined context for solving a task, then hand off to development. Use when the user asks to solve/implement a task ("solve PRI-4", "/reviewer_solve-task <key or description>", "реши задачу X"). Reads a keyed task from the reviewer store, pulls related/similar tasks and relevant code, distills a brief, and enters brainstorming. Requires the reviewer MCP server.
Build or update the reviewer base index (vector store + code graph) from a local repo clone. Use when the user asks to "index the codebase", "build the index", "sync the code", "rebuild the graph", "просиндексируй код", "построй индекс".
Configure or update a repo's .review.yml context layer and generic task-board metadata without secrets. Use when the user asks to set up or tune review config, context depth, ignored tracked paths, retrieval limits, or board selection.
Review a GitHub pull request with the RAG + code-graph pipeline (reviewer MCP server). Use when the user asks to review a PR ("review PR 123", "заревьюй PR", a PR URL). Requires ParadeDB/Neo4j running and a built base index.
Create a task on a configured board with canonical server-side structure. Use when the user asks to file or create a task on the board.
Warm the task graph and vector store by synchronizing a configured task board through the reviewer MCP server. Use when the user asks to sync or index board tasks.