Analyze git commit history to narrate a code file's evolution.
npx skills add https://github.com/tomwangowa/agent-skills --skill code-story-teller
Please help me install this Agent Skill. Skill: code-story-teller Source: https://github.com/tomwangowa/agent-skills/tree/main/code-story-teller Command: npx skills add https://github.com/tomwangowa/agent-skills --skill code-story-teller
This Skill helps developers understand the history and evolution of their codebase, making it easier to grasp design decisions, track changes, and onboard new team members.
Tell me the story of src/api/auth.js.
High-intent search queries and answers about installing and using this skill.
Yes, you can trace git history to onboard new team members by generating a narrative story of code evolution. It highlights key milestones, design rationale, and contributor patterns, making complex modules easier to grasp before refactoring.
You track code evolution by analyzing the git commit history for that specific file. This process identifies the file's origin, key milestones, design decisions, current state, and contributor history to narrate its development story.
Yes, analyzing git history works for understanding refactoring decisions in complex modules. It extracts the evolutionary story and design rationale from commit history, helping you grasp why specific architectural choices were made before you start refactoring.
Yes, you can generate a code evolution narrative in Traditional Chinese while retaining English technical terms. The analysis supports this bilingual output format to explain design decisions and code history for local development teams.
JustineDevsManage git repository history with atomic commits and interactive rebasing.
olivermorgan2Draft standardized Architectural Decision Records as markdown files in a git repository.
KrismithReddy12Calculate a weighted 0-10 code quality score from linters and test runners.
srnicholsGenerates release notes from Git history and CHANGELOG files.
