用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/tools-only/X-Skills --skill clean命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | clean |
| description | Remove old sprint directories with safety checks and archiving options |
| argument-hint | [--all | --keep-latest | --keep N] |
You are cleaning up old sprint directories.
Sprint directories contain valuable artifacts:
The user is responsible for:
ls -la .claude/sprint/
Show the user:
Ask the user which sprints to clean:
Options:
Before deletion, verify:
# Check for uncommitted changes
git status --porcelain .claude/sprint/
If there are uncommitted changes, WARN the user:
WARNING: You have uncommitted changes in sprint directories.
Uncommitted files:
[list files]
Recommendation: Commit your changes before cleaning.
git add .claude/
git commit -m "Checkpoint before cleanup"
Continue anyway? (y/N)
Based on user choice:
Clean all:
rm -rf .claude/sprint/*/
Keep latest:
LATEST=$(ls -d .claude/sprint/*/ | sort -V | tail -1)
find .claude/sprint/ -mindepth 1 -maxdepth 1 -type d ! -path "$LATEST" -exec rm -rf {} +
Keep N latest:
ls -d .claude/sprint/*/ | sort -V | head -n -[N] | xargs rm -rf
Select specific:
rm -rf .claude/sprint/[selected]/
After cleanup:
Cleanup complete.
Removed:
- .claude/sprint/1/
- .claude/sprint/2/
- ...
Remaining:
- .claude/sprint/[N]/
Tip: Create a checkpoint now:
git add -A && git commit -m "Cleanup old iterations"
For quick cleanup without prompts:
/sprint:clean --all - Remove all sprints
/sprint:clean --keep-latest - Keep only the latest
/sprint:clean --keep 3 - Keep the 3 most recent
Instead of deleting, offer to archive:
# Archive sprints before deletion
tar -czf .claude/sprint-archive-$(date +%Y%m%d).tar.gz .claude/sprint/
Then proceed with deletion.
Always remind the user:
REMINDER: You are responsible for checkpointing your work.
Before cleaning, consider:
1. git add .claude/ && git commit -m "Checkpoint"
2. Push to remote if you want off-machine backup
3. Keep sprint specs if you might need to reference them
Sprint artifacts are valuable documentation of:
- Architectural decisions
- API contracts
- Implementation reports
- Test results