commit

0xmsc's avatarfrom 0xmsc

Helps write conventional commit messages, create atomic commits, and follow git best practices. Use when the agent needs to help with git commits, commit message writing, or git workflow guidance.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026
[Developer Tools]

When & Why to Use This Skill

This Claude skill streamlines the version control process by helping developers write standardized Conventional Commit messages and maintain atomic commit structures. It ensures git best practices are followed by analyzing staged changes, drafting concise subject lines, and providing detailed explanations for complex updates, ultimately improving repository maintainability and team collaboration.

Use Cases

  • Standardizing Commit Messages: Automatically generating messages that follow the Conventional Commits specification (feat, fix, chore, etc.) to ensure a clean, readable, and searchable project history.
  • Maintaining Atomic Commits: Guiding the user to break down large changes into smaller, logical, and independent commits, which simplifies code reviews and makes debugging or rollbacks more efficient.
  • Workflow Guidance for Best Practices: Providing safe git command suggestions and structured workflow steps to help developers adhere to professional version control standards while avoiding destructive operations.
namecommit
descriptionHelps write conventional commit messages, create atomic commits, and follow git best practices. Use when the agent needs to help with git commits, commit message writing, or git workflow guidance.

Commit Skill

Workflow

  1. Analyze Results: Review git status and git diff --staged.
  2. Draft Message: Follow Conventional Commits.
    • feat, fix, docs, style, refactor, test, chore.
    • Max 50 chars for subject.
    • Explain "why" in body if needed (wrap at 72).
  3. Atomic Commits: Ensure one logical change per commit.
  4. Templates: Use assets/commit-template.txt for consistency.

Safe Git Commands

  • git add <files>
  • git commit -m "message"
  • git diff --staged
  • git status, git show, git log --oneline

Limitations

  • No interactive commands (git add -p, git rebase -i).
  • No force pushing or amending without explicit user guidance.
  • Always confirm before final commit/push.