Generate Conventional Commits headers from staged Git changes.
npx skills add https://github.com/lonewolfyx/skills --skill git-commit-message-lonewolfyx
Please help me install this Agent Skill. Skill: git-commit-message Source: https://github.com/lonewolfyx/skills/tree/main/skills/git-commit-message Command: npx skills add https://github.com/lonewolfyx/skills --skill git-commit-message-lonewolfyx
Generates semantic, validator-friendly Git commit headers that conform to Conventional Commits and Angular-style messaging, while aligning with repository-specific rules such as scripts/verify-commit.js. It helps when Codex needs to inspect staged changes, determine a valid commit type, draft a correct header, or rewrite an invalid one.
Draft a commit message for your staged changes using the git-commit-message tool.
High-intent search queries and answers about installing and using this skill.
To write a conventional commit message that passes local validators, draft a semantically correct header from staged changes by selecting a valid type, applying Angular-style formatting, and aligning with repository-specific rules like verify-commit scripts.
Format breaking changes in an Angular-style commit message by appending an exclamation mark after the optional scope, signaling the breaking change directly in the commit header before writing the subject.
You need an optional scope in a conventional commit header when your staged changes affect a specific module or package, requiring you to encapsulate the semantic context within the commit type and exclamation mark indicators.
Yes, this conventional commit generator works with custom verify-commit scripts by inspecting staged changes and fulfilling local constraints, ensuring the drafted message aligns with repository-specific validation rules.
The best way to automate drafting a valid git commit type from staged changes is to parse the semantic diff and select the most appropriate type from the repository's allowed set, formatting a concise subject that adheres to conventional commits.
Your commit message fails repository validation despite using conventional commits because it likely violates local constraints, requiring you to validate the type against the repository's allowed list and ensure the header format adheres to scripts like verify-commit.js.
ian-pascoeGenerate conventional git commit messages and stage related file changes.
fcakyonCreate standardized Git commit messages from staged changes.
sunLeeeValidate Git commit messages against Conventional Commits rules.
storm-softwareGenerate conventional commit messages for staged Git changes.
