菜单
Inspect and optionally remove completed Doradb task worktrees and their local branches with deterministic safety checks. Use when listing cleanup candidates or pruning implemented, clean, fully pushed task worktrees from the main dispatch checkout; never delete remote branches.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Design and resolve RFC documents through evidence-gated multi-round workflow. Use when planning large architectural/program-level changes in docs/rfcs, enforcing goal/scope/direction clarity, explicit first-principles/long-term/original-fit proposal lenses with rationale, draft-to-formal progression, and resolve-time synchronization with task/backlog outcomes plus readiness validation.
Audit branch-diff Rust files, or explicitly requested file/directory Rust targets, for Doradb coding style using deterministic tooling and concise read-only review. Use when asked to check coding style, run a style audit/style auditor, validate task-branch Rust changes during $task-resolve, or report style violations in branch-modified files.
Design and create implementation-ready Doradb task documents through deep repository research, strict RFC complexity gating, two proposal and review rounds, explicit user approval, and isolated task worktree creation. Use when planning a feature or bug fix into docs/tasks, including work sourced from backlog items or RFC phases.
Resolve implemented Doradb task documents after code, tests, review, and behavior verification are complete. Use when running the mandatory style gate, recording implementation outcomes, managing deferred or source backlogs, refreshing task ids, and synchronizing a parent RFC phase without committing or pushing.
Create and list GitHub Issues with deterministic scripts. Use when validating planning-document paths, converting docs/tasks or docs/rfcs into trackable GitHub issues with required type labels and default priority handling, or listing existing issues in this repository.
Manage backlog todo documents in docs/backlogs with deterministic tooling. Use when manually creating backlog items with duplicate checks, especially deferred follow-ups discovered during in-progress task/RFC work that need recoverable context, or closing/archiving backlog items with explicit reasons.
| name | task-prune |
| description | Inspect and optionally remove completed Doradb task worktrees and their local branches with deterministic safety checks. Use when listing cleanup candidates or pruning implemented, clean, fully pushed task worktrees from the main dispatch checkout; never delete remote branches. |
Use this skill only from the main dispatch worktree. The underlying tool calls
this operation purge-worktrees; keep that command name unchanged.
tools/task.rs purge-worktrees
main worktree with reason main_dispatch_branch..worktrees/ whose basename is a
six-digit task id, using that worktree's own
docs/tasks/<task-id>-*.md document.status: implemented;safe_to_purge, unfinished, and excluded, with
reasons for every non-safe worktree.tools/task.rs purge-worktrees --apply
Apply mode may act only on direct children of the dispatch root matching
.worktrees/<six-digit-task-id>. It may remove only:
git worktree remove;git branch -D.Never delete a remote branch. Treat missing task documents, non-implemented status, dirty worktrees, missing remote branches, or unpushed local tips as hard reasons to retain the worktree.