erk-exec
erk exec Guide
Quick Start
Before running any erk exec command, check syntax with -h:
erk exec <command> -h
Commands by Workflow
PR Review Operations
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 123- Make code changes
erk exec resolve-review-thread --thread-id PRRT_xxx
Plan Operations
When 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) |
Session Operations
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 |
Marker Operations
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.
Full Reference
For complete syntax details on all 65+ commands:
@reference.md
More from dagster-io/erk
dignified-code-simplifier
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.
96dignified-python
Production Python coding standards with automatic version detection (3.10-3.13). Use when writing,
77cli-skill-creator
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.
72command-creator
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.
72learned-docs
This skill should be used when writing, modifying, or reorganizing
71session-inspector
>
71