Creates Git commits from analyzed changes with conventional message formats.
npx skills add https://github.com/shonenm/dotfiles --skill commit-shonenm
Please help me install this Agent Skill. Skill: commit Source: https://github.com/shonenm/dotfiles/tree/main/common/claude/.claude/skills/commit Command: npx skills add https://github.com/shonenm/dotfiles --skill commit-shonenm
This Skill automates the creation of well-formatted Git commits by intelligently splitting your changes into logical units and generating descriptive messages, ensuring a clean and understandable commit history.
prefix(scope): description) for clarity and automation.Use the commit skill to create commits for all changes made during this session.
High-intent search queries and answers about installing and using this skill.
Automating conventional commit messages involves analyzing uncommitted changes, segmenting them into logical units, and generating prefixed messages like 'feat' or 'fix' for each atomic commit. This process ensures a clean, understandable Git history without manual message crafting.
Splitting a coding session into atomic Git commits requires analyzing modifications made during the session and dividing them into distinct logical units. Each unit is then staged and committed separately with a descriptive conventional commit message.
Yes, you can generate Git commits for all uncommitted modifications by analyzing the working directory and automatically staging files into logical units. This process segments changes and applies conventional commit formats without requiring manual git add commands.
Yes, preventing sensitive files like .env from being committed is a built-in precaution. The commit generation process analyzes changes and explicitly avoids staging sensitive environment files to ensure secure code management.
Conventional commit prefixes like 'feat', 'fix', and 'docs' are needed when you want to automate Git history parsing and maintain a structured changelog. They provide clarity by categorizing logical changes into atomic commits with standardized messages.
Logical change segmentation for Git commits works by analyzing a set of modifications and dividing them into distinct, atomic units based on their purpose. Each unit is then assigned a conventional commit prefix and description to ensure a clean history.
rintiEvaluate uncommitted git diffs with Codex CLI review feedback.
SynkraAIManage GitHub repositories and automate CI/CD workflows with quality gates.
queen-of-codeStandardize Git workflows with conventional commits and branch protection rules.
vab1997Generate conventional git commit messages from diffs with type and scope detection.