菜单
Iterative code refactoring through progressive lenses via a worker-reviewer agent team.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Nullables — testing technique alternative to using mocking libraries. Use when writing unit tests, when code touches external I/O or state (HTTP, databases, files, clock, random) anywhere in its dependency chain, when making a system testable, or when tests are slow or flaky.
Bash script style guide. Always use when writing bash scripts, shell scripts, or CLI bash tools.
Drive a browser from the terminal with playwright-cli: snapshot the page, then act on elements by ref. Use when automating browser interactions, filling web forms, testing UIs, or driving logged-in web apps from the command line.
Facilitates deep, structured learning of a topic — gathering source material, assessing the learner's gaps, then teaching through guided Socratic sessions. Use when someone wants to genuinely study or be tutored on a subject over time, not get a quick answer.
Creates C4 architecture diagrams for designing, documenting, or understanding software architecture. Use when working through system design, mapping existing codebases, or visualizing structure at any level from system landscape down to code.
Test-driven development (TDD) process used when writing code. Use whenever you are adding any new code, unless the user explicitly asks to skip TDD or the code is exploratory/spike.
| name | refactoring-team |
| description | Iterative code refactoring through progressive lenses via a worker-reviewer agent team. |
| disable-model-invocation | true |
| argument-hint | [target-path] |
| hooks | {"TeammateIdle":[{"hooks":[{"type":"command","command":"${CLAUDE_SKILL_DIR}/references/guard-idle-worker.sh"}]}]} |
STARTER_CHARACTER = 💎
Agent teams must be enabled in settings:
{
"env": {
"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
}
}
If not set, offer to add it before proceeding.
If $ARGUMENTS provided, use as target path. Otherwise ask for:
Verify the target path exists and tests pass before proceeding.
Generate a short random ID: head -c 3 /dev/urandom | xxd -p | head -c 3
Use it to name the teammates:
worker-ID (e.g. worker-a3f)reviewer-ID (e.g. reviewer-a3f)Read the spawn prompts:
Before spawning, replace these placeholders in both prompts:
TARGET_PATH → actual target pathTEST_COMMAND → actual test commandLENSES_DIR → ${CLAUDE_SKILL_DIR}/references/lensesGUIDES_DIR → ${CLAUDE_SKILL_DIR}/references/reviewer-guidesWORKER_NAME → the worker's name (e.g. worker-a3f)REVIEWER_NAME → the reviewer's name (e.g. reviewer-a3f)Tell the user:
teammateMode: "tmux" in settingsWhen a worker goes idle, read .refactoring-state to check the lens number. If it skipped a value, message the reviewer to go back and complete the skipped lens first.