Skip to main content

plannotator-user-code-review

Request a code review from the user via plannotator. Use at the end of an implementation task, or when the user asks for a review cycle. Collects structured annotations, then addresses each item.

Informações da origem

Repositório
jamiebrynes7/dotfiles
Última atividade na origem
7 de setembro de 2026 às 14:28
Idioma detectado do SKILL.md
inglês
Estrelas
0
Forks
0

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Exibindo SKILL.md

SKILL.md
Instruções da origem · Visualização somente leitura
name
plannotator:user-code-review
description
Request a code review from the user via plannotator. Use at the end of an implementation task, or when the user asks for a review cycle. Collects structured annotations, then addresses each item.
cc:allowed-tools
Bash(plannotator:*)
Plannotator provides a structured review UI where the user can leave inline annotations on specific files and lines. Use it to get precise, actionable feedback. Run the following command to start a review session. Set the Bash tool timeout to 1800000ms (30 minutes) so the user has enough time to review and annotate. ``` plannotator review ``` Plannotator starts a local HTTP server. If the execution environment sandboxes localhost socket creation, run the command using its narrowest available permission-escalation mechanism. Otherwise, run it normally. If Plannotator reports that its entire port range is exhausted in a sandboxed environment, treat that as a possible socket-permission failure rather than immediately changing ports; retry once with permission to bind a localhost socket. ## Reviewing Feedback For each annotation from the user: 1. **Summarize** the feedback in one line 2. **Evaluate** whether the suggestion is valid — push back if it would introduce a bug, conflict with project conventions, or reduce code quality 3. **Act** — apply the fix or explain why you disagree If no changes were requested, acknowledge this and move on.
Ver no GitHub