Iterative code refactoring through progressive lenses via a worker-reviewer agent team.
73%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/refactoring-team/SKILL.mdSTARTER_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.
saski/arnesto
752f690
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.