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/dotclaude 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]
tools
Delegate implementation to codex (coder) via the herdr-agentchat plugin and drive a two-pane conversation to completion.
development
Extract recurring patterns from past closed PRs/issues and the research findings in workspace/research/, verify them against the latest code, and propose them to docs/wiki/ via PR.
development
Create Decision Records (DR) in MADR v4 format with auto-numbering.
development
Detect flaky tests by shaking them — repeated runs under varied order, parallelism, and seed — plus a static smell scan that flags latent flakiness in tests that currently pass. Classify each target as confirmed-flaky, latent-flaky, or stable and fix the root cause without weakening the test. Do NOT use to fix a confirmed single bug (use /fix) or for static-only code review (use /audit).