resolve-dispute

Solid

Resolves stuck review findings via a put-up-or-concede exchange. Invoked by the facilitator when a finding survives arbitration without new evidence.

AI & Automation 85 stars 7 forks Updated 1 months ago MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
64
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
74
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

A review finding is stuck. Structure its resolution in three steps. **Step 1 — Frame the dispute.** Identify and state aloud: - The disputed finding (one sentence) - Who holds it - The facilitator's prior arbitration ruling (one sentence) **Step 2 — Send the reviewer this message, substituting `[finding]` with the actual finding:** > Your finding — [finding] — was arbitrated. To keep it open, you must provide ONE of: > (a) A concrete failure scenario: specific inputs or conditions that produce wrong behavior > (b) A source citation: file, line number, and what it shows > (c) A direct counterexample to the arbitration reasoning > > One response. No response counts as concession. After that, the facilitator rules and the finding is DECIDED. **Step 3 — Rule and tag.** After the reviewer responds: - Evidence present → the facilitator evaluates it on the merits and rules. Tag the finding DECIDED regardless of outcome. - No evidence → the facilitator tags DECIDED, asks the reviewer to re-score. - No response → the facilitator tags DECIDED. DECIDED findings cannot be re-raised without new substance. This enforces the existing "Don't regurgitate decided points" rule. **What this skill must not do:** - Override a finding backed by real evidence - Auto-resolve — the facilitator still decides after hearing the evidence - Apply to first-round disagreements — use normal arbitration first - Suppress legitimate concerns — evidence always reopens the door

Details

Author
DheerG
Repository
DheerG/swarms
Created
5 months ago
Last Updated
1 months ago
Language
Shell
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

fix-findings

Fix the findings from an independent-review report. Follow-on to the independent-review skill, but never run it automatically after a review: the user reads the report first and decides. Only run when the user explicitly invokes /address-findings or explicitly asks to address the review findings.

1 Updated 4 days ago
renatodvc
Code & Development Listed

comment-resolve

Verify whether an author's response to a review finding (a reply or a code change without a reply) actually resolves a thread I started, then recommend whether to resolve it and whether to revote. Follow pr-review for resolution criteria and unblocking conditions. The caller performs scanning, retrieval, resolution, voting, and platform API calls.

0 Updated today
qnamy
AI & Automation Listed

finding-reconciliation

Merge the independent A/B/C findings tables into one adjudicated ledger in `07-verification/documentation-verification-report.md` — normalizing to the finding schema, deduplicating by location and claim, recording per-finding corroboration without downgrading single-pass findings, promoting cross-pass disagreement to its own Critical finding, and splitting repairs into agent-repairable and owner-decision. Use when all three verification passes have returned their findings at Phase 9, or when ingesting an externally-produced audit. This skill MUST be consulted because publishing the findings table before repair is what makes the audit trail real, and because treating a lone dissenting pass as noise is exactly the correlated-error failure the three-pass design exists to prevent.

6 Updated today
synaptiai