测试与安全

ce-resolve-pr-feedback

everyinc/compou…g-plugin

Judge PR feedback centrally, apply valid fixes, and complete review conversations with publication verified. Use when addressing feedback already left on a PR, preparing local fixes for a caller to publish, or completing a saved feedback batch. Use ce-code-review for reviewing code before feedback exists.

  • 3248 次安装
  • 2.6万 星标
  • 收录于

安装命令

npx skills add https://github.com/everyinc/compound-engineering-plugin --skill ce-resolve-pr-feedback

SKILL.md

Resolve PR Review Feedback

Judge fresh PR review feedback centrally, then dispatch generic subagents seeded with the bundled fixer prompt only for approved fixes. Publish the fixes before replying and resolving. Resume completes saved judgments without another fix pass.

Done: Every selected item has a verdict and verified conversation completion or a reported residual. Completed threads have a visible submitted reply with quoted context and authoritative resolution; needs-human threads stay open. Ordinary and pipeline runs publish valid fixes before completion. Return-to-caller preserves its local fix commit and exact pending actions in a readable validated handoff, or records actual no-change completion. Resume verifies fresh publication and returns checkpointed completion or pending saved actions with retry evidence. Pending actions are never reported as resolved.

Escalations never block. Return needs-human with structured decision_context for the caller to show the user; leave its threads open with natural replies when the execution mode permits publication. Never pause mid-run to ask. A decision needing judgment rather than missing authority goes through ce-pov before escalation, as the rubric's "Adjudicate before escalating" section defines.

mode:pipeline publishes and completes feedback unattended. Read references/pipeline-mode.md before acting; it owns typed decision returns, trajectory-based non-convergence, and per-root invariant keys.

Caller authority: Invocation never grants authority beyond the caller's inherited user scope. Pipeline can fix, commit, push, reply, resolve and tick eligible checklist findings. Return-to-caller owns preparation; resume owns saved completion. All three exclude merge, rebase, force-push and CI approval, and never call a blocking-question tool. Narrow the scope when necessary; an excluded action becomes a needs-human residual.

mode:return-to-caller: Read references/return-to-caller.md before fetching or editing. Validate and commit fix-owned changes locally, never push. A fix batch saves its entire remote tail for caller publication, including reply-only items, human acknowledgments, resolutions and checklist ticks. A no-change batch may complete through the existing remote protocol and records actual progress.

mode:resume handoff:<path>: Read references/resume.md before PR detection or remote action. Complete only saved replies, resolutions and checklist ticks after fresh publication proof. Do not repeat judgment, edits, validation, commits or pushes. Unknown publication or invalidated context remains pending.

Default to fixing fresh feedback, including nitpicks. Judge each item on its merits regardless of source or form. Divert only on concrete evidence encountered while reading the code. Read references/evaluation-rubric.md before judging; it defines the reasons to divert and their evidence.

PR findings checklist: For each bullet in an existing ## Unapplied review findings section whose file and concern a published fix closes, tick it to - [x]; never add to, reorder, or create that section, or use it to record escalations. Return-to-caller saves intended ticks until publication is verified.