Run CodeWhale terminal coding agent workflows
Use CodeWhale as a local terminal coding agent for repository edits, test repair, provider-switched sessions, approval-gated commands, MCP tools, skills, and hooks.
npx skills add agentskillexchange/skills --skill run-codewhale-terminal-coding-agent-workflows
npm install -g codewhale, then run codewhale for the TUI or codewhale exec "fix the failing tests and explain what changed" for a non-interactive repository task. Use the first-run setup to connect a provider or stay offline; see the installation guide for Cargo, Docker, Nix, Scoop, prebuilt archives, Android/Termux, and mirror options.Use CodeWhale when an operator wants a coding agent to work directly in a repository from the terminal with explicit control over model provider, approval mode, sessions, goals, and command execution. The repeatable workflow is to install the CLI, open the TUI or run `codewhale exec`, ask it to fix or inspect a codebase task, review its plan and approvals, and let it read files, edit code, run commands, inspect results, and continue toward the goal. Invoke this instead of using a hosted coding product normally when the work needs local-first terminal access, provider-neutral model choice, offline/local model options, MCP servers, skills, hooks, saved sessions, or visible approval boundaries. The scope is the operator workflow for running guarded terminal coding tasks with CodeWhale, not a broad listing for every CodeWhale feature or a generic Rust CLI/framework entry.
What this skill actually does
Inputs and prerequisites: Node.js and npm, or Cargo/Docker/Nix/Scoop/prebuilt binary; terminal; optional MCP-compatible tools, skills, hooks, local model runtime, or hosted model provider key.
Setup notes: Install with npm install -g codewhale , then run codewhale for the TUI or codewhale exec “fix the failing tests and explain what changed” for a non-interactive repository task. Use the first-run setup to connect a provider or stay offline; see the installation guide for Cargo, Docker, Nix, Scoop, prebuilt archives, Android/Termux, and mirror options.
Source and verification boundary: use https://codewhale.net/ as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.