run-history-pipeline

When to use this skill

Extract failure-mode practices from a repository's git history. Runs two steps in order, clearing context between them (/clear in Claude Code, or clear context in Cursor):

1. mine-history (/mine-history in Claude Code or @mine-history in Cursor) → reads git log, produces _analysis/directives.md, _analysis/architecture.md, and _analysis/incidents.md
2. synthesize (/synthesize in Claude Code or @synthesize in Cursor) → reads _analysis/incidents.md, produces _analysis/extracted_skills_history/*/SKILL.md + plugin.json

Supports --from [step-name] to start from a specific step, e.g. /run-history-pipeline --from synthesize (Claude Code) or @run-history-pipeline --from synthesize (Cursor).

Note: This pipeline is optional. If you only want to analyze the codebase's current design (not its history), run /run-analysis-pipeline (Claude Code) or @run-analysis-pipeline (Cursor) instead.

---

Step 1 — Read pipeline state

Check for _analysis/.history-pipeline-state. Read it if it exists.

State file format:

completed: mine-history
next: synthesize
remaining:
published: false

Parse completed, next, remaining, and published fields. If the file doesn't exist, all steps are pending and mine-history is next.

If --from [step-name] was passed:

• Set next to the specified step
• Set completed to all steps that precede it in the pipeline order
• Set remaining to all steps that follow it
• Proceed with this overridden state (do not require a state file to exist)

If the state file shows both steps completed and published: false (or published field absent):

"All 2 pipeline steps are done. Skills are in _analysis/extracted_skills_history/.

Run /curate-skills (Claude Code) or @curate-skills (Cursor) to review and clean up, then /publish-skills (Claude Code) or @publish-skills (Cursor) to create a PR."

Then stop.

If the state file shows all steps completed and published: true: