Runs an automated sweep to drain a task queue, building and committing tasks one by one.
Install
mkdir -p .claude/skills/sweep && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17571" && unzip -o skill.zip -d .claude/skills/sweep && rm skill.zipInstalls to .claude/skills/sweep
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Drain this repo's .agent/tasks/ queue autonomously and run-to-completion, taking EACH task to a ship-ready bar — claim a 00_todo/ task (`coop tasks claim`), build it, gate it green, self-review it against the .agent/rules KB and every hat, ITERATE until clean, COMMIT it on its own, then `coop tasks done` — without quitting early. Arms the Stop-hook sentinel. Use to "work all the tasks" / drain a backlog / run an unattended sweep.Key capabilities
- →Claim tasks from the 00_todo/ queue
- →Build and gate each task to a ship-ready bar
- →Self-review changes against house rules and AGENTS.md
- →Iterate on tasks until clean and ready for commit
- →Commit each task individually with a focused message
- →Archive completed tasks to 99_done/ or block to 50_blocked/
How it works
The skill autonomously processes tasks from a queue, claiming each one, building it to a ship-ready state, self-reviewing against defined rules, and committing it. It repeats this cycle until the task queues are empty.
Inputs & outputs
When to use sweep
- →Draining a project backlog
- →Running unattended task sweeps
- →Automating repo maintenance tasks
About this skill
/sweep — drain the queue to a ship-ready bar, one commit per task
Run the work loop to completion. Claude scopes the queue Stop hook above to this skill's
lifetime; runtimes with a persistent goal/tracker use that too. Scope: this repo's
.agent/tasks/ (a task is a folder; its state is its directory — coop tasks lists
and moves them).
Be agentic. Each task is taken to a ship-ready bar: built, gated, then
self-reviewed from every angle it touches and iterated until clean — and only
then committed, on its own. The bar is not "it compiles"; it's "I'd defend
this in review from every hat and it breaks no house rule." The house rules
are the spine: this repo's AGENTS.md and the worked examples in .agent/rules/.
Build to them, then check the diff against them.
1. Prepare
- Set the runtime's persistent goal/tracker when it exists: do not stop until every scoped task is
committed and archived or properly blocked, and both
00_todo/and10_in_progress/are empty. - Read
AGENTS.mdin full (the gate and the contract),.agent/tasks/README.md, and every.agent/rules/*.md(the taste KB). Ifcoopis on PATH, runcoop tasks; otherwise inspect the queue state directories directly to announce the open00_todo/count.
2. The loop — claim the next task, repeat until 00_todo/ and 10_in_progress/ are empty
- Claim — if
coopis on PATH, runcoop tasks claim <id>; otherwise move the task folder from00_todo/to the existing10_in_progress/directory yourself. Do this first, so a parallel agent won't grab it. A task already in10_in_progress/is a prior attempt — resume it: read itsstate.md, thengit status/git diff. - Build — wear the hats; obey
AGENTS.md, match.agent/rules/and the surrounding style exactly./specfirst if it spans more than one file (writes the task'sspec.md)./verify-apibefore calling anything you're not certain exists. - Gate green — the repo's exact gate (
AGENTS.md→ "The gate"). No green, no review, no commit. - Self-review the diff from every angle it touches — correctness, security / abuse path, UX, tests (including the failure path), docs, readability — against the house rules. Fix what you find; iterate until you'd defend it.
- Commit — one focused commit for this task; keep
log.md(the what + why) current. - Final snapshot — after the commit, refresh
state.mdin10_in_progress/: preserve the useful summary and traps, setStatustocomplete, and setNext actiontonone. - Done — as the final filesystem action, if
coopis on PATH runcoop tasks done <id>; otherwise move the task folder to the existing99_done/directory yourself. A finished task is moved, never deleted — leave it in99_done/; never runcoop tasks rm(pruning the archive is the human's call). Blocked instead? Fill indecision.md(question · options · recommendation), then usecoop tasks block <id>when available or move the folder to the existing50_blocked/directory yourself. - Spot unrelated work? Use
coop backlog addwhen available, or create a self-contained folder under.agent/tasks/xx_backlog/, then return to the queue — don't derail the current task.
3. Finish
- When
00_todo/and10_in_progress/are empty, run a completeness pass: re-check every task you moved to99_done/againstgit log— gate green and a commit exists. Reopen anything that doesn't hold up withcoop tasks claim <id>when available, or move it back to10_in_progress/, and go again. - Report: tasks shipped, anything parked in the backlog or
50_blocked/, gate status.
When not to use it
- →When the goal is to stop before all tasks are complete
- →When the quality bar is only 'it compiles'
- →When ignoring house rules or AGENTS.md
Limitations
- →Requires adherence to AGENTS.md and .agent/rules/
- →Does not stop until 00_todo/ and 10_in_progress/ are empty
- →Each task must be taken to a ship-ready bar
How it compares
This skill enforces a rigorous, iterative build-gate-review-commit cycle for each task, ensuring a high-quality, ship-ready outcome, unlike simply building or committing without thorough self-review.
Compared to similar skills
sweep side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| sweep (this skill) | 0 | 17d | No flags | Advanced |
| run-nx-generator | 5 | 2mo | Review | Intermediate |
| upgrading-expo | 3 | 3mo | Review | Intermediate |
| bump-go-dependencies | 1 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by AndrewDryga
View all by AndrewDryga →You might also like
run-nx-generator
nrwl
Run Nx generators with prioritization for workspace-plugin generators. Use this when generating code, scaffolding new features, or automating repetitive tasks in the monorepo.
upgrading-expo
sickn33
Upgrade Expo SDK versions
bump-go-dependencies
docker
Update direct Go module dependencies one by one, validating each bump with tests and linter, committing individually, and producing a summary table for a PR description
flutter-pub-update
bannzai
Flutterプロジェクトのpubspec.yamlパッケージを更新するスキル。一括更新または指定パッケージ更新に対応。メジャーバージョン更新時は確認を挟み、更新前にpub.dev/GitHubでchangelogを確認して変更内容を報告する。$ARGUMENTSにパッケージ名を指定するか、--allで全パッケージ更新。
swarm-coordination
joelhooks
Multi-agent coordination patterns for OpenCode swarm workflows. Use when work benefits from parallelization or coordination.
coderabbit-local-dev-loop
jeremylongshore
Configure CodeRabbit local development with hot reload and testing. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with CodeRabbit. Trigger with phrases like "coderabbit dev setup", "coderabbit local development", "coderabbit dev environment", "develop with coderabbit".