Generate conventional git commit messages from staged changes.
npx skills add https://github.com/Castrozan/.dotfiles --skill commit-castrozan
Please help me install this Agent Skill. Skill: commit Source: https://github.com/Castrozan/.dotfiles/tree/main/agents/skills/commit Command: npx skills add https://github.com/Castrozan/.dotfiles --skill commit-castrozan
This Skill helps developers craft git commits that follow conventional formats, include meaningful descriptions, and provide analysis of changes to improve traceability and review quality.
Describe the changes you want to commit, and ask the skill to generate a conventional, descriptive commit message. For example: "Please generate a commit message for the latest staged changes following the conventional commits spec."
High-intent search queries and answers about installing and using this skill.
To generate conventional commit messages, analyze your staged git changes to determine scope and impact, then enforce a standardized structure like feat: or fix: to yield meaningful descriptions for consistent version control history.
The conventional commits format standardizes git messages using prefixes like feat: and fix: to indicate change types. Using it improves traceability, ensures consistent history, and enhances code review quality across projects.
Yes, automated commit message generation applies to any repository workflow including docs and config files. It analyzes staged changes to produce conventional, descriptive messages regardless of the file type.
The best way to write descriptive git commit messages is to automate change analysis on staged files, determining scope and impact to generate summaries that include rationale and follow conventional formats.
No, integrating conventional commits does not require manual formatting. Automation enforces the standardized structure and guides you through staging and committing, producing a clean, reusable history automatically.
You need to enforce a conventional structure for git commits when you want to improve traceability and review quality across projects, ensuring that all changes adhere to a standardized format for consistent history.
fusengineDetect conventional commit types from git changes and file patterns.
ccfGenerate CHANGELOG.md from commits, PRs, and releases using Keep a Changelog.
julianobarbosaAutomate Git commits with pre-commit security scans and Conventional Commits enforcement.
74nu5Generate conventional commit messages from diffs and stage files.
