Menú
Review and address all open PR comments — fetch, triage, implement changes, resolve, and summarize.
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
This skill should be used when the user needs to automate browser interactions, test UI workflows, verify page elements, take screenshots, upload files to forms, or interact with web applications during development and debugging. Use this skill for testing PDF upload dialogs, form interactions, dropdown selections, and visual verification of web pages.
Execute tasks from a tasks.yaml by orchestrating code-writer agents
Plan a feature using the prd-planner subagent
Break down a PRD into tasks following the task YAML spec
Manage tmux sessions, windows, and panes from the CLI — list state, read pane output, send keys/commands, create or kill sessions and windows, and inspect long-running terminal work. Use this skill whenever the user mentions tmux, asks to check what's running in another terminal, wants to start a background process in a tmux session, send a command to a running pane, capture or tail output from a tmux pane, attach context from a pane, or troubleshoot a stuck tmux process — even if they don't explicitly say "tmux command."
Plan a feature using the prd-planner subagent
| name | w-pr-feedback |
| description | Review and address all open PR comments — fetch, triage, implement changes, resolve, and summarize. |
Review and address all open comments on the current pull request.
Fetch PR context — run gh pr view to get the PR number and description, then gh pr comments and gh api repos/{owner}/{repo}/pulls/{pr}/reviews to collect all reviewer comments and inline code comments.
Triage each comment — for every comment, determine:
gh api without code changesImplement changes — make code edits for actionable feedback. Read the relevant files before modifying them. Keep changes scoped to what the comment asks.
Resolve each comment — after addressing or deciding not to act, post a reply using the gh CLI:
gh api repos/{owner}/{repo}/pulls/comments/{comment_id}/replies -f body="<response>"
Summarize — report back what was changed, what was replied to without changes, and anything that needs the user's input before proceeding.