Generate structured git commit messages with headers and detailed bodies.
npx skills add https://github.com/T1nker-1220/.claude --skill git-best-practices
Please help me install this Agent Skill. Skill: git-best-practices Source: https://github.com/T1nker-1220/.claude/tree/main/skills/git-best-practices Command: npx skills add https://github.com/T1nker-1220/.claude --skill git-best-practices
This Skill eliminates vague or incomplete commit messages that hinder code review, debugging, and understanding project history, leading to wasted time and increased technical debt.
git status and git diff --staged before generating any commit message, ensuring accuracy and completeness.feat(auth): add JWT token validation
New Functionality: Implement JWT validation middleware with token expiry checking and refresh token support.
Changes:
jwt-middleware.tsauth-service.ts to use middlewareImpact: Enhances security and session management.
High-intent search queries and answers about installing and using this skill.
Commit messages should follow a structured format with a concise header (type, scope, description) and a detailed body explaining the problem, root cause, solution, and changes. This ensures reviewers understand context and intent, reducing review cycles and improving code quality.
A complete commit message includes a header with commit type (feat, fix, refactor, docs, style, test, chore, perf), scope, and description, plus a body with sections for Problem, Root Cause, Solution, and Changes Made. This structure captures the full context needed for future debugging and maintenance.
Run `git status` to see staged and unstaged files, then use `git diff --staged` to review exact changes before generating your commit message. This verification prevents incomplete or incorrect commits and ensures your message accurately reflects what you're committing.
Commit types classify changes: feat adds functionality, fix resolves bugs, refactor improves code without changing behavior, docs updates documentation, style adjusts formatting, test adds tests, chore handles maintenance, and perf optimizes performance. Using the correct type keeps your version control history organized and searchable.
Yes. Detailed commit messages that explain problems, root causes, and solutions create a searchable historical record. When debugging, developers can use `git log` and `git blame` to understand why changes were made, reducing time spent investigating issues.
Structured commit messages are essential for teams. They provide consistent context across contributors, make code reviews faster, simplify onboarding, and reduce technical debt by ensuring the reasoning behind changes is documented for all team members.
david-nossebroCreate Conventional Commits messages from session context and git diffs.
sumrae412Automate conventional commits, pull requests, and 10-step code review before merging.
arakitakashiStandardize Git operations with Git Flow branching and Conventional Commits.
Greenmamba29Generate structured CHANGELOG.md entries from git commit history and semantic versioning tags.