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
Hand off the current task to a fresh background agent running in its own workmux worktree, passing a self-contained prompt synthesized from this conversation's context. Use when the user wants to outsource, delegate, or "hand off" implementation work to a separate agent session (e.g. "handoff this fix", "outsource it to a ccd agent", "spin up an agent to do X").
Delegate a code review to pi (`pi /skill:review`) running in a tmux window, then dispatch subagents to fix each finding and check it off the review file. Use when the user wants an automated review-and-fix loop over their current changes.
Teach a topic using the Feynman technique — explain simply, have the user re-explain, identify gaps, re-teach, and loop until they can explain it on their own. Use when the user wants to deeply understand a topic, test their understanding, or mentions "Feynman".
Build a focused 20-hour learning plan for a topic, structured as 10 two-hour sessions following the Pareto principle (20% that drives 80% of results). Use when the user wants to learn a topic fast, build a study plan, or create a structured curriculum.
Create or update a GitHub pull request for the current branch, committing pending changes first. Use when the user wants to open a PR, update an existing PR, or ship a branch for review.
Ask questions about specific GitHub code repositories using DeepWiki. Use when the user asks about a repo's code, architecture, configuration, modules, APIs, examples, or behavior and provides a GitHub repository in owner/repo form or as a GitHub URL.
| name | 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.