Generate conventional commit messages from git diffs.
npx skills add https://github.com/bilgrami/corporate-agent --skill commit-msg-bilgrami
Please help me install this Agent Skill. Skill: commit-msg Source: https://github.com/bilgrami/corporate-agent/tree/main/skills/commit-msg Command: npx skills add https://github.com/bilgrami/corporate-agent --skill commit-msg-bilgrami
Generating consistent, well-formed commit messages from diffs to improve readability and traceability in version history, following the conventional commits format.
Provide a well-formed commit message by analyzing git changes and applying conventional commit formatting.
High-intent search queries and answers about installing and using this skill.
Conventional commit messages from git diffs are generated by analyzing added, modified, and deleted content to determine type, scope, and subject. This assembles a complete message with optional body and footer, ensuring proper formatting and breaking-change handling.
The conventional commit format handles breaking changes by assembling a complete commit message with a specific type, optional scope, subject, optional body, and an optional footer. This ensures clear traceability and flags breaking changes according to conventional commit rules.
Yes, both staged and unstaged git changes can be analyzed for commit message generation. The tool detects added, modified, and deleted content across features, fixes, docs, and refactors to produce a well-formed conventional commit message.
To ensure commit subject length meets conventional commit guidelines, generate the message by analyzing git diffs and applying formatting rules. This guarantees the subject, body, and footer satisfy required length and formatting guidelines.
The best way to document refactors and fixes in version history is generating consistent conventional commit messages from git diffs. This improves readability and traceability by determining the correct commit type, scope, and subject for your changes.
Automated conventional commit message generation relies on analyzing git diffs to determine type, scope, and subject. It requires clear staged or unstaged changes to accurately detect added, modified, and deleted content, ensuring formatting guidelines are met without manual overrides.
notwillkAggregate git commits, uncommitted changes, and agent knowledge to list changed files.
TechDufusValidate Git commit messages for Conventional Commits format and limits.
bs-kooGenerate Korean Git commit messages from branch types and staged changes.
jeremylongshoreGenerates formatted commit messages from staged changes.
