Agent skill
code-story
Narrative templates for git history documentation. Used by /git:code-story command.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/code-story-majesticlabs-dev-majestic-marketplace
SKILL.md
Code Story Skill
Provides narrative templates for transforming git history into documentary-style stories.
Templates
Read the appropriate template based on detail level:
- resources/minimal-template.md - 1-2 page executive summary
- resources/standard-template.md - 5-10 page story with acts
- resources/comprehensive-template.md - 20+ page deep dive
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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?