← ClaudeAtlas

prompt-revisaolisted

Use right after marking a map task as done (feita) when that merge may have finished its topic (at the end of any map task, also inside /fila and /orquestrador), or when the user asks for the review prompt of a topic. Writes the final review prompt (plus an optional separate prompt for the sensitive part) into the topic's revisao field of the map.
thales8461/mapa-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill thales8461/mapa-skills
# prompt-revisao: review prompt for a finished topic When the last task of a topic becomes `feita: true`, the topic moves to "In review" and needs `revisao`: the prompt for an independent reviewer (another model or agent) that reads the code, runs the tests and writes a report. This skill writes that prompt. The `revisao` skill later triages the report. Helper: `node <mapa skill folder>/scripts/mapa.mjs` (read-only). Config: `.claude/mapa.json` (see `skills/mapa/references/config.md`). Reply in the project language (`language` in the config, default the user's). ## Step 1: did the topic finish? Right after writing `feita: true` (always after the merge): ```bash node <mapa>/scripts/mapa.mjs finished <task id> ``` - `PENDING` or `NOT FOUND`: nothing to do. Stop. - `FINISHED ... revisao ALREADY FILLED`: do not overwrite. Tell the user the prompt already exists. - `FINISHED ... paused`: do not write; tell the user. - `FINISHED ... revisao EMPTY`: go on. ## Step 2: gather the material (do not read the whole code) 1. Task ids and titles: `mapa.mjs summary` and the topic in the map. 2. PR of each task: `git log origin/main --first-parent --oneline -200` (merge commits name the branch). The last one is "main after PR #N". 3. `planFiles` and `progressFiles` from the config: the plan section of the topic, the decisions that look like defects but are accepted, and what each PR changed. If needed, `gh pr view <N> --json files --jq '.files[].path'`. 4. Tests of the changed parts, a