- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add Doist/todoist-cli --skill review-changes -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add Doist/todoist-cli --skill review-changes -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add Doist/todoist-cli --skill review-changes -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add Doist/todoist-cli --skill review-changes -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/Doist/todoist-cli/tree/HEAD/.agents/skills/review-changesDel publicador
Reviews cost several agent runs. Run them when the owner says the change is ready, or asks. During work, npm run verify is the check.
npm run verify passes.git ls-files --others --exclude-standard): they reach the reviewers and Doistbot's model providers. Gitignored files (.env, .tmp/) are not listed, and npm run review:worktree never copies them. Check every listed file for credentials, tokens and personal data; send none that holds them, and ask the owner about any file that does or that doesn't belong to the change. Never git add -A to tidy up.Done when the brief is written and the tree holds only the change, with no secrets or personal data in it.
src/lib/, command registration, global flags or argv handling in src/index.ts, the @doist/cli-core or @doist/todoist-sdk version, other package.json dependencies, build or CI config. It names the one fact that makes the change safe and proves it by running code. It looks where text search stops: library versions in package-lock.json, the shape of API responses, scripts and installed skills reading --json output, extensions receiving TD_* variables..agents/checks/, each with the brief and that check.Every brief says: the shared working tree is read-only. A reviewer that needs to run or break code makes its own copy with npm run review:worktree -- <dir>, then npm ci in it, and removes it after.
Use it when doistbot --version prints 1.0.12 or newer and doistbot doctor succeeds. Otherwise use the per-check subagents and tell the owner Doistbot was skipped.
doistbot review --json. In a stack: doistbot review --base <branch below> --json. Both cover commits, staged and unstaged edits, and untracked files. Nothing needs staging.doistbot review staged: it skips the branch's commits and still reports verified.status, verified and providerFailures first. An unverified review, or one with a failed provider, is partial: say so, and cover that gap with a subagent.Reviewers rate findings on the verify ladder. Take each to the rung its claim needs: the cited line for what the diff shows, a failing test or command for a behaviour claim. Then:
Look again when new evidence appears. Done when every finding has one of the three.
Fix, then npm run verify. A large fix gets its own task review. Report the findings with what happened to each, in the verify report format.
Reviews a finished change with fresh reviewers (a task review, a blast-radius review for shared code, and Doistbot or per-check subagents), then confirms each finding before acting on it. Use when the
---name: review-changesdescription: Reviews a finished change with fresh reviewers (a task review, a blast-radius review for shared code, and…---# .agents/skills/review-changes/SKILL.mdResumen general
Reviews a finished change with fresh reviewers (a task review, a blast-radius review for shared code, and Doistbot or per-check subagents), then confirms each finding before acting on it. Use when the owner says a change is "ready for a PR", "ready to merge" or ready for a release, or asks for "a review".
Preguntas frecuentes
Descarga .agents/skills/review-changes/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/Doist/todoist-cli.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.