ax-narrate

Solid

Write the agent-generated narration of the current session - the reviewable story of what changed, including what never reaches a PR (user corrections, abandoned attempts, tool failures). Triggers on "narrate this session", "summarize what changed", "write the session story", "narrate what we did", "session narration". Output is .ax/narrations/<session-id>.json for the ax studio narration view. Do NOT fire on "summarize this file" or generic recap questions answered inline - this skill writes a structured artifact.

AI & Automation 107 stars 13 forks Updated 2 days ago AGPL-3.0

Install

View on GitHub

Quality Score: 81/100

Stars 20%
68
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# ax:narrate - write the session's story as a structured narration You were there. This skill turns YOUR OWN memory of the session into a reviewable artifact: 3-7 stops in reading-flow order, each anchored to real evidence - code hunks, turn numbers, user quotes, failures. The point is to capture what a PR diff never shows: the corrections, the dead ends, the recoveries. The artifact validates against `SessionNarration` in `apps/studio/src/routes/narration-types.ts` and renders in ax studio. ## Step 1 - identify the session - Preferred: `ax sessions here --days=1 --json` and pick the current session's id (the one matching this conversation). Use the short id. - If `ax` is unavailable or the session isn't ingested yet, derive a slug: `<repo>-<YYYYMMDD-HHmm>`. Note in `meta` that turn seqs are best-effort ordinals in that case. - If available, `ax sessions show <id> --json` gives you the real turn seqs to anchor against. Prefer real seqs over guesses. ## Step 2 - reconstruct the story from your own context Re-read the conversation in your head before writing anything: 1. What did the user originally ask for? (intent) 2. What existed before, what exists now? (before/after) 3. Where did the user redirect or correct you? EVERY one of these becomes a `correction` anchor. No exceptions. 4. Which tool failures actually mattered (changed your approach, cost real time, forced a workaround)? Each becomes a `tool_failure` anchor. Skip trivial retries that changed ...

Details

Author
Necmttn
Repository
Necmttn/ax
Created
4 months ago
Last Updated
2 days ago
Language
TypeScript
License
AGPL-3.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category