القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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.
| name | reviewer_sync-tasks |
| description | 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. |
Reply in Russian. This is a thin, server-side trigger: the server enumerates, normalizes, and indexes the board. Do not enumerate tasks in the client and do not send credentials.
task_board from .review.yml; if absent, call get_board_config(). If neither resolves
a board, report a board-less no-op.type, project, create_target, done_target, and options.
Do not infer provider-specific fields.get_board_targets(board_type=<type>, project=<project>, provider_options=<task_board.options or {}>).
Its response contains targets and option entries with required_for and choices. Ask the
user to configure missing required options instead of inventing values; discovery is read-only.sync_board(board=<project or null>, board_type=<type>,
provider_options=<task_board.options or {}>, limit=<limit or null>,
purge_orphaned=<explicit request or false>)
by_board breakdown in Russian. Warnings and an error
response are fail-open: explain the reason and leave the local repository unchanged.sync_board is idempotent: rerunning is safe and inexpensive when the watermark is warm. It reads
the board; it never writes back.