Git

What it does

This skill automates common Git commands, helping you manage your code repositories effectively. It enforces best practices for commit messages using Conventional Commits format and guides users through a GitHub Flow workflow with branching strategies. The skill aims to streamline version control tasks by providing structured guidance and automating repetitive actions.

When to use it

• When creating new commits and needing to adhere to a consistent commit message format (e.g., feat: add ..., fix: resolve ...).
• When starting a new Git repository and wanting to establish a standard branching strategy like the one described in GitHub Flow.
• To ensure code changes are clearly documented with concise, informative commit messages that follow established conventions.
• For teams adopting or enforcing Conventional Commits for improved release note generation and project understanding.

Key capabilities

• Conventional Commit Enforcement: Guides users to write commit messages following the <type>: <description> format.
• Branching Strategy Guidance: Provides a recommended branching strategy based on GitHub Flow (main, feature branches, fix branches, refactor branches).
• Commit Message Formatting Rules: Offers detailed guidelines for crafting clear and concise commit messages including length limits, tense usage, and capitalization rules.
• Workflow Examples: Illustrates how to initialize repositories with main as the default branch.

Example prompts

• "Create a commit message for adding dark mode support."
• "What is the recommended branching strategy for this project?"
• "Show me an example of a Conventional Commit message for fixing a bug."
• “How do I change my repository's default branch to main?”

Tips & gotchas

• The skill relies on user input and understanding of Git concepts. It doesn’t replace the need for basic Git knowledge.
• While it guides commit message formatting, it does not automatically validate or enforce these rules; users must follow the guidelines provided.