What is Git Storytelling?

Git Storytelling is a philosophy of making small, frequent, and logical commits that read like a chronological narrative of how a feature or solution was built.

When should I avoid making a commit?

You should generally avoid committing when the code does not compile, tests are failing, or when you have mixed unrelated changes or sensitive data in your staging area.

Is it safe to rebase my commits using this strategy?

The skill provides guidance on when it is safe to rebase (local commits) versus when it is dangerous (pushed commits), helping you maintain a clean history without disrupting collaborators.

How does this help with code reviews?

Small, focused commits allow reviewers to follow your logic step-by-step rather than digesting one massive, confusing change, leading to faster and more thorough approvals.

Does this skill support Conventional Commits?

Yes, it utilizes standard prefixes like feat, fix, refactor, and docs to categorize changes clearly and make the history easily searchable.

Git Storytelling & Commit Strategy

Name: Git Storytelling & Commit Strategy
Author: TheBushidoCollective

byTheBushidoCollective

•

开发者工具

Implements professional Git commit patterns to create a clear, chronological narrative of your software development process.

This skill guides Claude in adopting an atomic commit philosophy, ensuring that every change to the codebase is documented through small, logical, and well-described commits. It provides structured patterns for commit messages—using standard prefixes like feat, fix, and refactor—while helping developers determine exactly when to commit and when to hold back. By focusing on the 'story arc' of development, from initial setup to final polish, this skill helps create a maintainable and navigable project history that simplifies debugging, enhances code reviews, and adheres to professional software engineering standards.

主要功能

01Guides developers on interactive rebasing to clean up local history before pushing

0297 GitHub stars

03Enforces atomic commit patterns for single logical changes

04Provides standardized commit message prefixes for better history categorization

05Differentiates between stable checkpoints and work-in-progress code

06Automates descriptive commit message generation with proper co-author attribution

使用场景

01Building complex features where a step-by-step history is required for effective code review

02Executing large-scale refactors by breaking them into safe, incremental, and reversible steps

03Managing a structured bug-fix workflow including reproduction tests and verification

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add thebushidocollective/han commit-strategy

For use in Claude.ai and ChatGPT

Download Skill