claudegoodies
Skill

ax-extract-workflow

From sickn33

Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.

Facts

Status
Actively maintained
Last commit

Source preview

The instructions Claude Code reads when this skill runs.

# ax Extract Workflow

## Overview

Use this skill to reconstruct the workflow behind a past coding-agent artifact:
a shipped feature, PR, demo, refactor, report, or other concrete result. It uses
the local `ax` graph to connect commits, sessions, turns, skills, and tool traces
into a short "how this got made" narrative.

`ax` must be installed, available on `PATH`, and able to reach its local database.
If ax cannot connect to its DB, report the connection failure and stop instead of
guessing from memory.

## When to Use This Skill

- Use when the user asks "how did we build X?", "what made X work?", or "extract the workflow behind this artifact."
- Use when the anchor is a commit SHA, date, feature name, PR, session, or repo-local artifact.
- Use when the user wants the sequence of agent skills, prompts, commands, decisions, and checks that led to a result.
- Do not use for a generic activity summary; use normal session listing instead.

## How It Works

### Step 1: Resolve the Anchor

Identify the best anchor from the user's request:

- Commit SHA: use it directly.
- Date or date range: inspect sessions around the date.
- Topic, feature, or artifact name: search recall for related turns, commits, and skills.
- "This repo recently": list recent sessions for the current repo.

```bash
ax recall "live ingest dashboard" --sources=turn,commit,skill --scope=here
ax sessions near ab
View full source on GitHub →

Other skills