ax-extract-workflow
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.
Profile →npx skills add sickn33/agentic-awesome-skills --skill ax-extract-workflow --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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,
- Overview
- When to Use This Skill
- How It Works
- Step 1: Resolve the Anchor
- Step 2: Pick Relevant Sessions
- Step 3: Inspect the Session Trail
- Step 4: Write the Reconstruction
- Examples
- Reconstruct a Feature from a Commit
- Reconstruct Work Around a Date
- Best Practices
- Limitations
- Security & Safety Notes
- Related Skills
ax recall "live ingest dashboard" --sources=turn,commit,skill --scope=here ax sessions near abc1234 --json ax sessions around 2026-06-15 --days=3 --json ax sessions here --days=14 ax sessions show <session-id> --json ax sessions show <session-id> --by-role ax recall "specific keyword from the artifact" --sources=turn,commit --scope=here ax sessions near 8f31c2a --json ax sessions around 2026-06-15 --days=2 --json ax recall "otel receiver" --sources=turn,commit,skill --scope=here
What does the ax-extract-workflow skill do?
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill ax-extract-workflow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.