Menú
Use when asked to review code comments for accuracy/quality or explicitly asked to run the comment-analyzer subagent.
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.
Basado en la clasificación ocupacional SOC
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning
Use when receiving UAT feedback, bug reports, user testing results, stakeholder feedback, QA findings, or any batch of issues to investigate. Investigates each item BEFORE creating issues, classifies by type and priority, creates well-formed GitHub issues with proper project board integration.
MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gates that other skills MUST call. No work proceeds without project board compliance.
Use for LARGE work requiring feature-level grouping. Creates epic tracking issues, manages related issues under a common label, tracks epic progress, and coordinates with milestones.
Use when the user wants to design Codex agent equivalents (specialized workers/profiles/prompt files), define triggering conditions, or build reusable agent prompts and validation tools.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
| name | comment-analyzer |
| description | Use when asked to review code comments for accuracy/quality or explicitly asked to run the comment-analyzer subagent. |
Use the comment-analyzer agent card to handle this specialized task.
codex-subagent comment-analyzer <<'EOF'
[Provide the task context, scope, and any issue/PR numbers.]
EOF