swarm-pr-feedback

Ingest and resolve pull request feedback with iterative verification lanes and bot reviews.

1|Updated May 17, 2026
One-click install
npx skills add https://github.com/djimit/djimitflo --skill swarm-pr-feedback-djimit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swarm-pr-feedback
Source: https://github.com/djimit/djimitflo/tree/main/.opencode/skills/swarm-pr-feedback
Command: npx skills add https://github.com/djimit/djimitflo --skill swarm-pr-feedback-djimit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires swarm-pr-review, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of resolving known pull request feedback, ensuring all issues are addressed without dropping findings.

Core Features & Use Cases

  • Feedback Ingestion: Intake feedback from pasted PR comments, GitHub review threads, and CI/check failures.
  • Verification: Use iterative verification lanes for classification and evidence collection.
  • Bot Reviews: Supports multi-round bot reviews with evidence verification and conflict resolution.
  • Use Case: For example, when reviewing a PR with numerous comments and feedback, this Skill can automate the process of verifying each item, fixing confirmed issues, and ensuring the PR is ready for merge.

Quick Start

Run the 'swarm-pr-feedback' skill to resolve all known issues in the current PR branch.

Frequently Asked Questions about swarm-pr-feedback

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

FAQPage Schema
How do I automate resolving pull request feedback and CI failures?

To automate pull request feedback resolution, you ingest PR comments and CI failures, then use iterative verification lanes to classify and fix confirmed issues. This ensures all findings are addressed without dropping any items.

What is the best way to handle multi-round bot reviews for code verification?

The best way to handle multi-round bot reviews is by applying evidence verification and conflict resolution protocols. This approach systematically verifies each feedback item to ensure code changes meet review standards before merge.

Do I need the swarm-pr-review skill to process GitHub review threads?

Yes, processing GitHub review threads requires the swarm-pr-review skill for handoff artifacts and verification protocols. It provides the necessary foundation for ingesting and resolving PR feedback iteratively.

Can I ingest CI check failures and PR comments together for issue resolution?

Yes, you can ingest CI check failures and PR comments together for issue resolution. The skill intakes feedback from pasted PR comments, GitHub review threads, and CI failures to classify and verify each item.

Why does resolving PR feedback manually lead to dropped findings?

Resolving PR feedback manually leads to dropped findings because tracking numerous comments and CI failures overwhelms manual verification. Iterative verification lanes automate evidence collection to ensure every issue is confirmed and addressed.

When should I use iterative verification lanes for code review feedback?

You should use iterative verification lanes for code review feedback when a PR has numerous comments requiring systematic classification and evidence collection. This ensures every issue is verified and fixed before the PR is ready for merge.