help
Route a "how do I use Codewhale" question to the installed help, config, and doctor surfaces instead of reciting a manual from memory. Explicit-only.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 4.1w
- Forks
- 3.6k
01 前言 Front Matter
- name
- help
- invocation
- explicit-only
- description
- Route a "how do I use Codewhale" question to the installed help, config, and doctor surfaces instead of reciting a manual from memory. Explicit-only.
02 资源文件 3
- 参考文档SKILL.generation-14.md2.4 KB
- 参考文档SOURCE.md339 B
- 参考文档TRUST.auto.yaml2.2 KB
03 SKILL.md 正文
Help
Invocation
Explicit-only. This skill is a router, not a manual. It is deliberately kept out of the ambient model catalogue so it never spends prompt budget, and it never restates documentation that the running build already exposes.
When to use
Load it only when the user explicitly asks how to use Codewhale itself — a command, a setting, a keybinding, or where a feature lives.
Non-goals
- Do not paste a manual, a command list, or a settings table into context.
- Do not answer from memory of another harness; Codewhale's surfaces differ.
- Do not guess at flags, config keys, or paths. Read them, or say you did not.
Routing table
Answer from the surface that owns the fact, in this order:
- Slash commands —
/helplists the commands this build registers;/help <command>prints that command's usage line. This is the only authoritative command list, because it is generated from the registry. - Skills —
/skillsopens the manager,/skills inspectprints the discovery mode, searched directories, and source paths./skill <name>activates one. Seedocs/SKILLS.mdin a Codewhale checkout. - Configuration —
/configis the live settings surface. Config file keys are documented indocs/CONFIGURATION.md; provider/model routing indocs/PROVIDERS.md. - Keybindings —
docs/KEYBINDINGS.mdin a checkout. There is no keybinding slash command; do not invent one. - Environment problems —
codewhale-tui doctorreports the resolved config path, provider credential presence (never values), and workspace state. Prefer its output over inference.
Working in a Codewhale checkout
When the workspace is a Codewhale checkout, docs/ is present on disk and
the read tool (path: "docs/...") is the right tool. Read the single most relevant file and quote
the specific lines. Outside a checkout, docs/ is usually absent — in that
case rely on /help, /config, and doctor, and say plainly that the
reference docs are not installed locally.
Bounds
- One surface per question. Do not sweep
docs/looking for context. - If a surface disagrees with your recollection, the surface wins.
- If nothing local answers it, say so and stop; do not invent a flag.
04 同仓库更多 Skills
gh-find-prs
Survey the open Codewhale PR and issue queue read-only: fetch each item, check it against current code, and produce one coverage and disposition matrix with cited evidence and credit owed.
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-close-issues
Close resolved Codewhale issues only after verifying the landed behavior: Refs #N per landing, Fixes #N only when the reporter's scenario was reproduced, closure at the release step or on the reporter's confirmation, always with a crediting comment.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
feedback
暂无简介
cw-slice
Use before writing code for any Codewhale feature, upgrade, or refactor: find the existing owner of the behavior, bound the change to one reviewable slice, and fix the evidence bar before you start.