skills/brush/SKILL.md
Enrich a vague prompt by routing to the best skill or injecting relevant rules and constraints. Use when prompt is rough or missing perspective. Examples: "find bugs", "refactor this", "add feature X", プロンプト補完, ブラッシュアップ. Do NOT use when the prompt is already detailed.
npx skillsauth add thkt/claude-config brushInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Route a vague prompt to the best skill, or enrich it with relevant rules and constraints when no skill fits.
$1: rough prompt (required). If empty, output usage example and exit.
| Step | Action | Detail |
| --- | --- | --- |
| 1 | Classify | Identify task type from $1: refactor / bug-fix / feature / review / investigation / other |
| 2 | Scan skills | Glob ~/.claude/skills/*/SKILL.md; read descriptions of 3–5 candidates that match the task type |
| 3 | Route or enrich | See decision below |
| 4 | Output | See format below |
A skill is a clear match when its "Use when" description covers the task.
Output the routing recommendation. Include any gap — what the skill does NOT cover — if the original prompt had scope the skill won't handle.
Rules from ~/.claude/rules/ are already loaded in context. Select the
relevant ones and make them explicit in the rewritten prompt.
| Category | Inject when | | --- | --- | | PRINCIPLES.md (Occam, DRY, YAGNI) | Refactoring, architecture decisions | | CODE_THRESHOLDS.md | Any code quality ask | | CODE_STRUCTURE.md | Structural or organization questions | | SECURITY.md | Auth, input handling, API endpoints | | PRE_TASK_CHECK.md | Broad implementation requests |
Only inject rules that are directly relevant. Do not add length for thoroughness.
→ /skill-name [suggested args]
Covers: [what the skill handles from the original prompt]
Gap: [what it does not cover, if any]
Original:
> [verbatim input]
Enriched:
> [rewritten prompt]
Added:
- [rule or principle]: [what was injected and why]
documentation
Generates and updates .claude/OUTCOME.md interactively. When the file is absent or empty (no Behavior / all sections TBD), collects content via AskUserQuestion and writes the stub; when present, shows the current state and applies updates.
development
Judge a SKILL.md against craft axes (single responsibility, description distinctiveness, imperative voice, verifiable completion, calibration, progressive disclosure) and apply the fixes the audit surfaces. Do not use for format-presence-only checks (use reviewer-prompt) or reproducibility loops (use /tuning).
tools
Internal helper for /think Step 11. Renders SOW.md + Spec.md as an integrated Astro view and returns a dev server URL.
development
Extract repository spec while detecting bugs, spec gaps, and consistency drift via dual-purpose documentation. OUTCOME.md-axis question-driven exploration with ephemeral output. Do NOT use for code review (use /audit or /polish), feature implementation (use /code), planning only (use /think), or single-bug fix (use /fix).