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.

Datos de origen

Repositorio
jamiebrynes7/dotfiles
Última actividad en el origen
7 de septiembre de 2026 a las 14:28
Idioma detectado de SKILL.md
inglés
Estrellas
0
Forks
0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
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 en GitHub