菜单
Run scripts/housekeep.py --apply and stage the regenerated task-system index files (OVERVIEW.md, EPICS.md, KANBAN.md, ideas OVERVIEW). Use this after any task-system file change instead of running the script directly.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Write Bash commands that don't trigger unnecessary permission prompts. Use Read/Edit/Grep instead of head/tail/sed/awk/cat/echo; split chained commands (&&, ;, ||) into separate Bash calls; drop diagnostic suffixes like `; echo "EXIT=$?"`. The allowlist matches whole command strings — every mismatch costs the user attention.
Commit user-named files atomically via scripts/commit-pathspec.sh (which wraps `git commit -m "..." -- <files>` and writes the provenance token the pre-commit hook validates). Applies the CLAUDE.md "Pre-commit hook failures on unrelated changes" protocol when the hook fails. Never adds --no-verify silently — explicit user approval is required.
Scaffold a new epic file in docs/developers/tasks/open/ and run housekeep
Scaffold a new idea file in docs/developers/ideas/open/ and regenerate the ideas OVERVIEW.md
Set a task to active — updates status, moves to active/, runs housekeep. Also resumes paused tasks (paused/ → active/ or active/ with closed prerequisites).
Mark a task as closed — writes effort_actual, moves the file to closed/, runs housekeep, and commits
| name | housekeep |
| description | Run scripts/housekeep.py --apply and stage the regenerated task-system index files (OVERVIEW.md, EPICS.md, KANBAN.md, ideas OVERVIEW). Use this after any task-system file change instead of running the script directly. |
Invoked as /housekeep whenever you would otherwise run
python scripts/housekeep.py --apply by hand — i.e. after any of:
status: change you didn't make via /ts-task-active /
/ts-task-done / /ts-task-pause / /ts-task-reopen (those skills
already invoke housekeep internally),docs/developers/ideas/,The skill is a thin wrapper that owns the canonical invocation, prints the move summary housekeep emits, and stages the regenerated index files so they ride along with whatever change triggered the regen.
Run housekeep:
python scripts/housekeep.py --apply
The script prints a summary of file moves and which index files it regenerated. Pass that summary through to the user verbatim — do not paraphrase, the move list is the receipt.
Stage the regenerated index files. Per the project's "OVERVIEW/ EPICS/KANBAN regen belongs in the status-change commit" rule, these are your output for the change that triggered this skill:
git add docs/developers/tasks/OVERVIEW.md \
docs/developers/tasks/EPICS.md \
docs/developers/tasks/KANBAN.md \
docs/developers/ideas/OVERVIEW.md
If any of those files is unchanged, git add is a no-op for it —
safe.
If housekeep performed file moves (the summary lists MOVE …
lines), also stage the moved task files. Each line has the form
MOVE <old-path> -> <new-path>; stage both paths so git records
the rename.
Do not stage anything housekeep did not touch. Per the project's "commit only your own work" rule, foreign working-tree changes from parallel sessions stay where they are.
Do not create a commit. The staged regen rides along with the change that triggered it — the caller commits.
/ts-task-active, /ts-task-done, /ts-task-pause,
/ts-task-reopen — those skills already run housekeep themselves.--check (read-only) audit. Run python scripts/housekeep.py
without --apply directly; this skill is the apply-side wrapper.Registered in .vibe/config.toml's
enabled_skills list per the project's CLAUDE.md skill-registration
rule.