code-story

Narrative templates for git history documentation. Used by /git:code-story command.

⭐13stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026⬇️3downloads

When & Why to Use This Skill

The Code Story skill automates the transformation of raw Git commit histories into engaging, documentary-style narratives. It solves the problem of fragmented and dry technical logs by providing structured templates that highlight key milestones, technical conflicts, and architectural evolutions, making complex codebase histories accessible to both technical and non-technical stakeholders.

Use Cases

  • Project Post-Mortems: Generating a comprehensive 'story of the build' to analyze major technical decisions, bottlenecks, and successful resolutions after a product launch.
  • Executive Summaries: Using the minimal template to provide high-level stakeholders with a concise 1-2 page narrative of development progress and key achievements.
  • Developer Onboarding: Creating a 'genesis story' of the codebase to help new hires understand the historical context, 'why' behind certain architectural choices, and the evolution of the project.
  • Release Notes & Changelogs: Enhancing standard changelogs with a narrative flow that explains the journey of a feature from its first commit to its final implementation.
  • Open Source Documentation: Crafting a compelling history of a repository to showcase project maturity and the human effort involved to potential contributors and users.
namecode-story
descriptionNarrative templates for git history documentation. Used by /git:code-story command.

Code Story Skill

Provides narrative templates for transforming git history into documentary-style stories.

Templates

Read the appropriate template based on detail level:

Narrative Guidelines

Voice and Tone

  • Documentary style: informative yet engaging
  • Third-person perspective
  • Acknowledge the human element
  • Find the drama in technical decisions
  • Celebrate achievements without hyperbole

What Makes a Good Code Story

  • Genesis moment: First commit sets the stage
  • Character development: Contributors evolve
  • Conflict and resolution: Bugs, refactors, breaking changes
  • Turning points: Direction-changing decisions
  • Present connection: Link past to current state

Commit Citation Format

  • Short SHA in backticks: abc1234
  • Include date and author for key commits
  • Link to GitHub if remote is github.com