Agent skill
minion-polish
PROACTIVELY USE after implementing code to add docstrings, type hints, cleanup. Delegates grunt work to local LLMs — saves cloud tokens. Files must be <500 lines. Use for mechanical polish, not logic changes. Changes are auto-applied.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/minion-polish
SKILL.md
Minion Polish
Dispatch local model to add mechanical polish. Changes are auto-applied.
When to Invoke
- After implementing a feature
- Files need docstrings, type hints, cleanup
- Mechanical changes only (no logic changes)
Command
source .venv/bin/activate && python scripts/minions.py --json polish <files> --task <task>
Tasks
| Task | Description |
|---|---|
all |
Docstrings + types + headers (default) |
docstrings |
Add function/class docstrings |
types |
Add type hints |
headers |
Add module-level docstrings |
Examples
# Polish single file
python scripts/minions.py --json polish src/foo.py --task all
# Multiple files
python scripts/minions.py --json polish src/foo.py src/bar.py --task docstrings
# Dry run
python scripts/minions.py --json polish src/foo.py --task all --dry-run
Output
{
"applied": true,
"files_modified": ["src/foo.py"],
"changes": ["src/foo.py: Added 3 docstring(s)"],
"errors": [],
"stats": {"total": 1, "applied": 1, "failed": 0}
}
Claude Integration
After completing code:
- Small (1-2 files): Auto-invoke, report summary
- Medium (3+ files): Ask user "Want me to dispatch minions for polish?"
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?