// Guide for erk exec subcommands. Use when running erk exec commands to understand syntax, find the right command for a task, or learn common workflows. Always check syntax with -h or load this skill before running erk exec commands.
This skill should be used when running CI checks iteratively and fixing failures. Use when executing make targets (fast-ci, all-ci, ci), iterating on lint/format/type/test errors, or needing the devrun agent pattern for pytest/ty/ruff/prettier/make/gt commands.
This skill should be used when creating a skill for a CLI tool. Use when users ask to document a command-line tool, create CLI guidance, or build a skill for terminal commands. Essential for systematically introspecting CLI tools through help text, man pages, GitHub repos, and online research, then organizing findings into effective skill documentation.
This skill should be used when working with cmux, the terminal multiplexer application. Use when users mention cmux commands, workspace management, terminal pane operations, or cmux integration with erk. Essential for understanding cmux's workspace model, CLI commands, and scripting patterns.
This skill should be used when creating a Claude Code slash command. Use when users ask to "create a command", "make a slash command", "add a command", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices.
Simplifies and refines Python code for clarity, consistency, and maintainability while preserving all functionality. Applies dignified-python standards. Focuses on recently modified code unless instructed otherwise.
Internal skill for commit message generation. Only load when explicitly requested by name or invoked by commands.
| name | erk-exec |
| description | Guide for erk exec subcommands. Use when running erk exec commands to understand syntax, find the right command for a task, or learn common workflows. Always check syntax with -h or load this skill before running erk exec commands. |
| metadata | {"internal":true} |
Before running any erk exec command, check syntax with -h:
erk exec <command> -h
When addressing PR review comments or resolving threads:
| Command | Purpose |
|---|---|
get-pr-review-comments | Fetch review comments (use --pr N) |
resolve-review-thread | Resolve a thread (use --thread-id) |
reply-to-discussion-comment | Reply to discussion comment |
get-pr-discussion-comments | Fetch discussion comments |
Typical workflow:
erk exec get-pr-review-comments --pr 123erk exec resolve-review-thread --thread-id PRRT_xxxWhen working with erk-prs:
| Command | Purpose |
|---|---|
plan-save | Save plan (backend-aware) |
get-pr-metadata | Get metadata from PR |
setup-impl-from-pr | Set up impl-context from PR |
get-issue-body | Fetch issue body (REST API) |
update-issue-body | Update issue body (REST API) |
When working with Claude Code sessions:
| Command | Purpose |
|---|---|
list-sessions | List sessions for current project |
preprocess-session | Compress session for analysis |
push-session | Push preprocessed session to learn branch |
download-remote-session | Download session from gist |
For inter-process communication:
| Command | Purpose |
|---|---|
marker create | Create marker file |
marker exists | Check if marker exists |
marker read | Read marker content |
marker delete | Delete marker file |
All marker commands require --session-id.
For complete syntax details on all 65+ commands:
@reference.md