Menu
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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
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.
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.
| name | reviewer_create-task |
| description | 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. |
Reply in Russian. The server assembles the canonical body (Проблема / Что сделать / Критерии приёмки / Контекст), so clients never implement board markup or send credentials.
task_board from .review.yml; otherwise call get_board_config(). Read
only type, project, create_target, done_target, and options. No board is a board-less
no-op: explain it in Russian and stop.problem, steps, criteria, and context. Ground problem with
search_codebase(...) and actual path:line evidence. Use technical Russian: no emoji,
decorative separators, or marketing tone.get_board_targets(board_type=<type>, project=<project>, provider_options=<task_board.options or {}>). Its response has targets and options:
each option declares required_for and choices. Use create_target only when it is among
create-purpose targets. If a required create option is absent, discover it or ask the user;
never guess. Empty discovery may create without a target only when no required option is missing.create_task(title=…, problem=…, steps=[…], criteria=[…], context=…,
board_type=<type>, project=<project>, target=<create_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 {}>). Report the task key, URL, warnings, and result.All reads stay fail-open. The confirmed create_task call is the only write.