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.
复制下面这句话,粘贴给 Claude Code、Codex、Cursor 等 AI 编程工具,它会读取安装说明并在你确认后完成安装。
请阅读 https://ai.atlankj.com/install/asset/gh-help-fab2233326c6 ,按照其中的说明把「help」安装到你(当前 AI 工具)中。执行前先告诉我将运行的命令和写入的位置,等我确认。
查看 AI 将读取的安装说明正在读取 GitHub 原文…
内容来自 GitHub 原始文件,由原作者维护。在 GitHub 查看
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.
Load it only when the user explicitly asks how to use Codewhale itself — a command, a setting, a keybinding, or where a feature lives.
Answer from the surface that owns the fact, in this order:
/help lists 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 opens the manager, /skills inspect prints the
discovery mode, searched directories, and source paths. /skill <name>
activates one. See docs/SKILLS.md in a Codewhale checkout./config is the live settings surface. Config file
keys are documented in docs/CONFIGURATION.md; provider/model routing in
docs/PROVIDERS.md.docs/KEYBINDINGS.md in a checkout. There is no
keybinding slash command; do not invent one.codewhale-tui doctor reports the resolved
config path, provider credential presence (never values), and workspace
state. Prefer its output over inference.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.
docs/ looking for context.