pull-request-feedback-loop
Handles PR review feedback by fetching comments, grouping issues, fixing one group at a time, and verifying before replies.
git clone --depth 1 https://github.com/ArchieIndian/openclaw-superpowers /tmp/pull-request-feedback-loop && cp -r /tmp/pull-request-feedback-loop/skills/core/pull-request-feedback-loop ~/.claude/skills/pull-request-feedback-loopSKILL.md
# Pull Request Feedback Loop PR feedback is a queue of review obligations, not a pile of comments. Use this skill when a user asks you to address PR comments, requested changes, failed checks tied to review feedback, or stale review threads. ## When to Use - A PR has unresolved review comments or requested changes - The user asks you to "address review feedback" or "fix PR comments" - You need to reconcile code changes, replies, and verification Do not use this for ordinary local refactors with no review thread. ## Process 1. Identify the PR. - Prefer the PR number or URL from the user. - If missing, run `gh pr status` or `gh pr view --json number,url,headRefName`. 2. Fetch review context. - Run `gh pr view <pr> --comments`. - If needed, run `gh api` for review threads or inline comments. - Capture author, file, line, status, and requested change. 3. Group comments by issue. - Merge duplicate comments that point at the same underlying fix. - Separate behavior bugs, test gaps, naming/docs cleanup, and questions. - Mark comments that need clarification before code changes. 4. Fix one group at a time. - Inspect the referenced code before editing. - Make the smallest coherent change for that group. - Avoid bundling unrelated cleanup into review fixes. 5. Verify before replying. - Run the narrowest relevant test or check for each group. - If no test can run, explain the exact reason and inspect manually. - Do not claim a thread is resolved until verification passes or is explicitly waived. 6. Prepare replies. - Summarize what changed and how it was verified. - Keep replies short and factual. - Do not submit replies automatically unless the user asked you to. ## Output Report: - Groups handled - Files changed - Verification run - Threads ready for reply - Threads needing user or reviewer clarification ## Guardrails - Do not force-push, delete branches, or dismiss reviews without explicit permission. - Do not mark comments resolved only because code was edited. - Do not ignore a comment because it looks small; either address it or explain why it is not applicable.
Syncs agent daily memory and MEMORY.md to an Obsidian vault so notes are human-browsable. Use nightly or on demand.
Structured ideation before any implementation. Use when starting any non-trivial task.
Scaffolds and validates new superpowers skills. Use when creating a new skill for this repository.
Executes plans task-by-task with verification. Use when implementing a plan.
Triggers a secondary verification pass for any agent output containing factual claims, numbers, dates, or named entities before the output is acted on
Crawls a new codebase to infer stack, conventions, and key invariants, then generates a PROJECT.md context file for the agent
Detects skill name shadowing and description-overlap conflicts that cause OpenClaw to trigger the wrong skill or silently ignore one when two skills compete for the same intent.
Reviews whether a skill will trigger reliably, guide useful behavior, avoid overlap, and produce testable outcomes.