Prunes stale or already-ruled cards from a kanban board's decision sections.
npx skills add https://github.com/mark-brannan/dotfiles --skill sweep-mark-brannan
Please help me install this Agent Skill. Skill: sweep Source: https://github.com/mark-brannan/dotfiles/tree/main/.claude/skills/sweep Command: npx skills add https://github.com/mark-brannan/dotfiles --skill sweep-mark-brannan
## Needs ruling and ## Solace's sections so only live, ranked questions remain. ## Core Features & Use Cases - Proof-based cleanup: Finds cards already ruled in ADRs, docs/decisions.md, requirements Q-nn entries, issue comments, or PRs, and proposes deletion with the proof attached. - Staleness detection: Flags cards whose subject disappeared — merged branches, archived repos, cut features, or passed until: events. - Reranking and triage dialog: Ranks survivors by what they block, then presents a multi-select where each ticked card gets exactly one action: Deleted, Answered, Deferred, or Dig. - Dry-run mode: --dry-run reports the same list without changing anything, and always runs at wrap-up. - Use Case: Before showing the board via worklist or /card-helper, run a sweep so stale rulings are removed and the remaining questions are ranked by what they block. ## Quick Start Ask the assistant to sweep the board and show which cards are stale or already ruled, with a dry run first.High-intent search queries and answers about installing and using this skill.
Run the sweep to check each card in the Needs ruling and Solace's sections for prior rulings or staleness. It proposes deletions with proof, then lets you confirm each action through a multi-select dialog before anything changes.
It looks where the answer would have landed: the linked ADR, docs/decisions.md, a requirements Q-nn entry, the issue's comments, or the implementing PR. A hit with a link counts as proof for proposing deletion.
Yes, run with --dry-run to get the same list of proposed deletions and reranked survivors without any dialog or edits. Dry runs also happen automatically at wrap-up, with results written to the log.
Answered cards are appended to docs/decisions.md in the project's primary repo with a date, short name, the answer, and a link, newest first. The card is then removed and the board is committed with the proof.
Learn cards under the Solace's section are never proposed; they drop only when explicitly confirmed. Cards in the Claude's section are also excluded since that queue is worked rather than tidied.
balamuruCoordinate GitHub Issues on a Kanban board using GitHub Projects v2.
openclawManage Trello boards, lists, and cards via REST API.
inkeepWrites architecture decision records as Nygard/MADR-shaped ADRs under a decisions directory.
devrelaicomGenerate and manage zero-knowledge proofs for Midnight transactions.