Skip to content
cccskills
FreePublished on GitHub

shell-builtins

Add or modify commands handled inside Crush's embedded shell before they reach the operating system. The guidance covers command routing, input and output streams, exit codes, and cancellation so commands work with pipes, redirection, and hook timeouts.

OriginalShow the original description

Use when creating a new shell builtin command for Crush (internal/shell/), editing an existing one, or when the user needs to understand how commands are intercepted in Crush's embedded shell.

See how to install

Good for

  • Adding a command to Crush's embedded shell
  • Modifying an existing built-in command
  • Supporting pipes and output redirection
  • Implementing cancellation for hook timeouts

Files included (1)

  • SKILL.md3.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Shell Builtins

Crush's shell (internal/shell/) uses mvdan.cc/sh/v3 for POSIX shell emulation. Commands can be intercepted before they reach the OS by adding builtins — functions handled in-process.

How Builtins Work

Builtins live in builtinHandler() in internal/shell/run.go. This is an interp.ExecHandlerFunc middleware registered in standardHandlers() before the block handler, so builtins run even for commands that would otherwise be blocked. The same handler chain is shared by the stateful Shell type and the stateless Run entrypoint used by the hook runner, so builtins are available identically in the bash tool and in hooks.

The handler is a switch on args[0]. Each case either handles the command inline or delegates to a helper function.

Adding a New Builtin

  1. Add the case to the switch in builtinHandler() in run.go.
  2. Get I/O from the handler context, not from os.Stdin/os.Stdout. This ensures the builtin works with pipes and redirections:
    case "mycommand":
        hc := interp.HandlerCtx(ctx)
        return handleMyCommand(ctx, args, hc.Stdin, hc.Stdout, hc.Stderr)
    
  3. Implement the handler in its own file (e.g., internal/shell/mycommand.go). The function signature must accept a context.Context as the first parameter, plus args, stdin, stdout, and stderr:
    func handleMyCommand(ctx context.Context, args []string, stdin io.Reader, stdout, stderr io.Writer) error {
        // args[0] is the command name ("mycommand"), args[1:] are arguments.
        // Write output to stdout, errors to stderr.
        // Return nil on success, or interp.ExitStatus(n) for non-zero exit codes.
    }
    
  4. Poll ctx in every unbounded loop. Builtins that iterate over input, emit values in a generator-style loop, or do any other work that can exceed a few milliseconds MUST check ctx.Err() on each iteration and return it verbatim when non-nil. Hook timeouts rely on this: an unbounded builtin that never polls ctx cannot be interrupted by a hook's timeout_sec, and the hook runner will have to abandon the goroutine (see internal/hooks/runner.go). Returning ctx.Err() (not interp.ExitStatus(n)) lets callers distinguish "command exited non-zero" from "we ran out of time".
    for _, item := range items {
        if err := ctx.Err(); err != nil {
            return err
        }
        // ... process item
    }
    
  5. Return values: return nil for success, interp.ExitStatus(n) for non-zero exit codes, or ctx.Err() on cancellation. Write error messages to stderr before returning.
  6. No extra wiring needed — builtinHandler() is already registered in standardHandlers().

Existing Builtins

CommandFileDescription
jqjq.goJSON processor using github.com/itchyny/gojq

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

builtin-skills

FreeSummary

Add or edit skills bundled with Crush, following guidance on file placement, required metadata, compile-time embedding, and discovery tests. It also explains how built-in skills are loaded and how user skills override them.

  • Adding a skill bundled with Crush
  • Editing an existing built-in skill
  • Understanding skill discovery and overrides
charmbracelet/crush28.7KUpdated Oct 19, 2026

crush-config

FreeSummary

Configure Crush with Bash or JSON files to choose AI providers and models, connect external tools, set permissions, and adjust behavior. Understand how project and global settings combine when customizing your working environment.

  • Set up AI providers and model selections
  • Connect MCP servers and language servers
  • Configure tool permissions and execution hooks
charmbracelet/crush28.7KUpdated Oct 19, 2026

crush-hooks

FreeSummary

Create, configure, and troubleshoot Crush hooks, commands that run before tool execution. Use them to block or approve calls, rewrite tool input, or add context for the agent, with guidance on configuration and troubleshooting.

  • Blocking destructive shell commands
  • Automatically approving read-only tools
  • Adding editing reminders for the agent
charmbracelet/crush28.7KUpdated Oct 19, 2026

jq

FreeSummary

Extract fields, filter records, and reshape JSON from API responses, configuration files, or logs using Crush’s built-in jq. Get help writing and debugging transformations, constructing new JSON, and formatting output for other commands.

  • Extract selected fields from API responses
  • Filter JSON arrays by conditions
  • Reshape configuration data or construct JSON
charmbracelet/crush28.7KUpdated Oct 19, 2026

See all skills by charmbracelet

Report a problem with this skill