swarm-pr-feedback

Ingests and resolves pull request feedback with verified fixes and closure ledgers.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/pandejesal/drone-nav-sar --skill swarm-pr-feedback-pandejesal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swarm-pr-feedback
Source: https://github.com/pandejesal/drone-nav-sar/tree/main/.swarm/bundled-skills/swarm-pr-feedback
Command: npx skills add https://github.com/pandejesal/drone-nav-sar --skill swarm-pr-feedback-pandejesal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Pull request feedback arrives scattered across review comments, bot reviews, CI failures, and merge conflicts, making it easy to drop findings or ship unreviewed changes. This Skill builds a complete feedback ledger, verifies every claim against source code, fixes confirmed issues, and reports closure status for every item. ## Core Features & Use Cases - Complete Feedback Ledger: Normalizes every review comment, CI failure, conflict, and bot finding into tracked FB-### items so nothing is silently dropped. - Skeptical Claim Verification: Classifies each item as CONFIRMED, DISPROVED, PRE_EXISTING, or NEEDS_USER_DECISION using source-level evidence, including dedicated protocols for bot security findings. - Multi-Round Bot Review Handling: Continues the ledger across iterative auto-review bot rounds with a 3-strikes evidence-escalation rule instead of re-triaging from scratch. - Mandatory Gate Discipline: Enforces structural pre-checks, reviewer and test gates, and a closeout gate before any fix lands or the PR is published. - Use Case: A reviewer bot posts new findings after every push to your PR. Use this Skill to triage each round, disprove false positives with code evidence, fix real issues, and post a per-round closure ledger comment. ## Quick Start Ask the agent to resolve all feedback on the current pull request using the swarm-pr-feedback workflow, verifying each review comment and CI failure before fixing.

Frequently Asked Questions about swarm-pr-feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve all PR review comments and CI failures systematically?

Build a complete feedback ledger assigning every comment, CI failure, and conflict an FB-### ID, then verify each claim against the source code before fixing. The closure ledger at the end reports a final status for every item so nothing is dropped.

How to handle a review bot that posts new findings after every push?

Continue the same feedback ledger across rounds instead of restarting triage. Carry forward unresolved items, mint fresh IDs only for new findings, and apply the 3-strikes evidence-escalation rule when the same finding reappears repeatedly.

Can automated security bot findings be false positives?

Yes, SAST bots frequently misflag patterns like RegExp.exec as command injection or miss existing schema validation. Verify every CRITICAL or HIGH finding by reading the actual source line and surrounding context before acting on it.

Does this workflow work without the plugin's controller tools?

Yes, it supports three runtime profiles: a mechanical controller, native parallel subagents, or a single-context sequential mode. Profiles B and C are first-class paths that maintain the ledger and gates manually.

When should a review finding not be fixed?

Do not fix findings disproved by source or test evidence, pre-existing issues not worsened by the PR, or suggestions that would add misleading guards. Record them in the closure ledger with the disproving evidence instead.