SkillHub ClubShip Full StackFull Stack

erk-exec

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.

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars

Hot score

Updated

March 20, 2026

Overall rating

C2.5

Composite score

2.5

Best-practice grade

S96.0

Install command

npx @skill-hub/cli install dagster-io-erk-erk-exec

Repository

dagster-io/erk

Skill path: .claude/skills/erk-exec

Open repository

Best for

Primary workflow: Ship Full Stack.

Technical facets: Full Stack.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: dagster-io.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

Install erk-exec into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
Review https://github.com/dagster-io/erk before adding erk-exec to shared team environments
Use erk-exec for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
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.
---

# erk exec Guide

## Quick Start

Before running any `erk exec` command, check syntax with `-h`:

```bash
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:**

1. `erk exec get-pr-review-comments --pr 123`
2. Make code changes
3. `erk exec resolve-review-thread --thread-id PRRT_xxx`

### Plan Operations

When working with erk-plans:

| Command              | Purpose                      |
| -------------------- | ---------------------------- |
| `plan-save`          | Save plan (backend-aware)    |
| `get-plan-metadata`  | Get metadata from plan       |
| `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