Menú
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/sapegin/dotfiles --skill agent-commentsEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Review a diff for local code quality, AI-generated slop, and polish in application code, configuration, documentation, and agent artifacts.
Review a diff for requirements, behavior, APIs, architecture, and maintainability across code, configuration, documentation and agent artifacts.
Audit every local skill for predictable behavior, sound structure, and prompt quality.
Basado en la clasificación ocupacional SOC
Mostrando SKILL.md
| name | agent-comments |
| description | Scan project for agent code comments and fix them. |
| disable-model-invocation | true |
Find and fix every AI: comment in the current project.
From the project root (or the path the user gave):
agent-comments
Empty output means there is nothing to fix — say so and stop.
Each comment is a block:
path/to/file.ts:42
The instruction text
Blocks are separated by a blank line. The first line is file:line; the rest is the instruction.
Work through every comment before re-scanning.
AI: comment only after an actionable instruction has been fixed.Prefer fixing comments in dependency order when one fix clearly unblocks another (types before callers, shared helpers before usages).
Re-run agent-comments after all fixes. Repeat the fix loop until the scanner reports no comments or every remaining comment has been deliberately skipped. If skipped comments remain, report that the scanner is still non-empty and why each comment was retained.
Then run the project’s usual validation (tsc, linter, tests) when available. Fix failures caused by your changes.
Summarize:
file:line — one line on what changedIf nothing was found initially, one sentence is enough.