Analyze uncommitted Git changes and generate conventional commit messages.
npx skills add https://github.com/gufranco/dotfiles --skill commit-gufranco
Please help me install this Agent Skill. Skill: commit Source: https://github.com/gufranco/dotfiles/tree/main/claude/skills/commit Command: npx skills add https://github.com/gufranco/dotfiles --skill commit-gufranco
This Skill automates the process of creating well-formatted, semantic Git commits, ensuring a clean and understandable project history.
feat(auth): implement two-factor authentication with a detailed body explaining the implementation.Use the commit skill to analyze all uncommitted changes and create a semantic commit.
High-intent search queries and answers about installing and using this skill.
This skill analyzes uncommitted Git changes and generates semantic commits following the conventional commit format. It stages file diffs and evaluates commit history to ensure logical grouping and informative project history.
The conventional commit format structures semantic commits like `feat(auth): implement two-factor authentication` to maintain understandable code history. You need it in software development workflows requiring a structured commit history for automated versioning and clear feature tracking.
Yes, this skill analyzes uncommitted Git changes to group them logically into a single semantic commit. It reads file diffs and evaluates existing commit history to determine the most appropriate conventional commit type and scope for the staged changes.
Yes, this skill requires the Git CLI to stage changes, diff files, and log commit history for analysis. The CLI provides the necessary version control data to evaluate uncommitted changes and generate accurate semantic commit messages.
The best way to maintain clean code history is automating semantic commits that follow the conventional commit format. This skill analyzes uncommitted Git changes and generates structured messages with detailed bodies explaining the implementation, ensuring consistency across your project.
Conventional commits enforce a structured format that creates a clean, understandable project history, unlike standard Git commit messages. This semantic structure allows for automated version control analysis and clearly distinguishes features, fixes, and other change types.
mkittAnalyze uncommitted Git changes to propose logical commit groupings.
CuriousLearnerGenerates project changelogs from Git commits using standard formatting.
opmauCreate conventional commits from staged git changes with confirmation.
alvarosanchezAnalyze diffs and stage files to create Conventional Commits.