Find answers about Codewhale commands, settings, skills, and keyboard shortcuts using the installed help and configuration tools. For environment problems, consult diagnostic output to explain what the current installation actually supports.
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.
Review the instructions the agent will receive before you install.
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.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Split a large goal into clearly bounded tasks that can run in parallel. Coordinate existing agent and worktree tools, then combine and verify the results. The skill starts only when explicitly requested.
Generate independent options for design, implementation, explanations, or debugging, then compare them using one shared rubric. Code candidates use separate working copies and undergo independent verification before a winner is presented for review.
Check Codewhale release readiness through ordered tests, builds, version checks, and manual terminal checks. Record command results and observed behavior, including responsiveness, route isolation, and follow-up input handling, while explicitly identifying any skipped checks.
Operate desktop apps and isolated browsers on registered computers by inspecting interface controls, entering information, and checking results. The skill also covers screenshots and recording, with separate routing for the user's signed-in Chrome through Chromewhale.
Check a local Codewhale checkout before contributing: inspect branch and sync status, build the CLI, and run the repository’s CI checks. Present recent commits and changelog entries from local files, with clear status for each step.
Builds and installs Codewhale with a source revision identifier, then verifies the installed version in a fresh shell. It guides hands-on runtime checks for interface behavior, routing, approvals, and other changes that automated tests may miss.