Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From swarmdo-adr
Read back adr-patterns + adr-edges namespaces, surface dangling refs / supersede cycles / status mismatches; exit 1 on cycles
How this skill is triggered — by the user, by Claude, or both
Slash command
/swarmdo-adr:adr-verifyThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Companion to `adr-index`. After import, reads the persisted graph and surfaces integrity issues:
Companion to adr-index. After import, reads the persisted graph and surfaces integrity issues:
adr-patterns. Common cause: the referenced ADR is in a sibling repo or got deleted.ADR-A supersedes ADR-B and ADR-B supersedes ADR-A (or longer cycles). Always data corruption.supersedes edge but its own status isn't Superseded. Usually a missed status update during a successor ADR's promotion.adr-index to confirm the graph is healthyVERIFY_STRICT=1 exits 1 on any issue)node plugins/swarmdo-adr/scripts/verify.mjs
Optional env:
VERIFY_FORMAT=json — JSON instead of markdownVERIFY_STRICT=1 — exit 1 on ANY issue (default: only on cycles)| Code | Meaning |
|---|---|
0 | Graph healthy (or dangling refs / status mismatches present in non-strict mode) |
1 | Supersede cycle detected, OR strict mode + any issue present |
adr-index — populates the data this skill verifiesscripts/import.mjs — has its own dry-run validation; this skill is the read-back companionnpx claudepluginhub swarmdo/swarmdo --plugin swarmdo-adrGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.