Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
The English summary is being prepared. Showing the original description.
Clean up git worktrees across your repos: list every worktree, classify it as merged, remote-only, local-only or dirty, recap what each holds, and remove only the merged clean ones after GO. Use for "clean up worktrees", "what is in my aos-wt folders", "land my worktrees", "prune worktrees".
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
What you get: an inventory of your worktrees with a class for each, and the merged clean ones removed after your GO.
git rev-parse --path-format=absolute --git-common-dir, parent dir)<owner/repo> for each repo comes from git -C <repo> remote get-url origingit -C <repo> worktree list --porcelain → inventory table (path, branch, HEAD) in the run log — the main worktree, the worktree running this playbook, and any entry marked locked or prunable are keepgh auth status (fails → log it, skip the squash predicate, only ancestry merges count); git -C <repo> fetch origin --prune; default branch: default=$(git -C <repo> symbolic-ref --short refs/remotes/origin/HEAD); default=${default#origin/} (the command prints origin/main) → both in the run log — fetch fails → log it, classify against the local refs, mark the table "stale"dirty: git -C <wt> status --porcelain --ignored shows anything other than !! entries; !! (ignored files, deleted by removal) are listed per row in the GO line<branch>): always local-only, never removedmerged: git -C <repo> merge-base --is-ancestor <branch> origin/<default>, or (squash merge) gh pr list -R <owner/repo> --head <branch> --state merged --json number,headRefOid has a PR whose headRefOid equals the worktree HEAD (git -C <wt> rev-parse HEAD); a reused branch name with a different headRefOid does not countremote-only: the upstream exists and git -C <wt> rev-list --count @{u}..HEAD is 0 (safe on the remote, unmerged)local-only: everything else; commits exist only herepr-recap; if it cannot be built log git -C <wt> log --oneline origin/<default>..HEAD and git -C <wt> diff --stat origin/<default>...HEAD instead — one recap or fallback per rowmerged and not keep, shown in full with these exact commands per row: git -C <repo> worktree remove <path> (label the row merged (empty) when git -C <repo> rev-parse <branch> equals git -C <repo> rev-parse origin/<default>; never --force; git refuses dirty trees), then git -C <repo> branch -d <branch> (-d refuses squash-merged branches → log "branch kept, needs -D, human decides"; never -D). The run stops here until the human types GO. GO covers exactly that list, once. The hook does not cover these commands, so this GO is their only guard. Never remove dirty, remote-only, local-only or keep rows, and never use rm -r.git -C <repo> worktree list → removed paths are gone, kept rows unchangedRun log: production_artifacts/pb-worktrees-land-<date>.md in the start directory, never committed
Rules
N. done|skipped|failed — artifact — check result) and WAITING FOR GO: <step> at each gate.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
The English summary is being prepared. Showing the original description.
Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
The English summary is being prepared. Showing the original description.
Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.
The English summary is being prepared. Showing the original description.
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.
The English summary is being prepared. Showing the original description.
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
The English summary is being prepared. Showing the original description.
agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.
The English summary is being prepared. Showing the original description.