Analyzes repository changes to generate conventional git commit messages.
npx skills add https://github.com/arowinski/dotfiles --skill commit-arowinski
Please help me install this Agent Skill. Skill: commit Source: https://github.com/arowinski/dotfiles/tree/main/claude/skills/commit Command: npx skills add https://github.com/arowinski/dotfiles --skill commit-arowinski
What problem does it solves? This Skill automates the creation of clear, concise, and convention-compliant commit messages. It eliminates the guesswork and manual effort involved in staging changes and writing commit descriptions, leading to a cleaner, more understandable version control history.
Commit my current changes, focusing on the bug fix I just implemented.
High-intent search queries and answers about installing and using this skill.
Commit messages should follow conventions like conventional commits, using an imperative mood subject line under 80 characters plus an optional body with bullet points. This Skill automates message generation by analyzing your changes and applying project-specific formatting rules, ensuring consistency without manual effort.
Yes. This Skill analyzes your modified files, determines the primary purpose of your changes, intelligently stages relevant files while avoiding sensitive data, and generates a convention-compliant commit message—eliminating manual staging and message composition.
Use this Skill to automatically detect your change type—bug fix, feature, refactor, configuration, or docs—analyze the scope, and generate an appropriate commit message in conventional format with a descriptive subject and detailed body referencing affected code.
It performs status and diff analysis to classify changes by type and scope, then generates a first-line imperative subject under 80 characters and an optional body with bullet points using third-person narration and code references—all aligned with conventional commits.
No. This Skill intelligently stages relevant files automatically based on your modifications, avoiding unrelated changes and sensitive data, so you can commit without remembering staging rules or file selection logic.
This Skill analyzes the primary purpose of your modifications to determine the dominant change type and scope. For mixed changes, it generates a message reflecting the main intent while capturing significant modifications in the body with code references.
dr-robert-liInitialize Git repositories and manage staged commits in WordPress builds.
korallisGenerates changelogs from Git history, commit messages, and pull requests.
dhntReplay feature branch commits onto an updated base with conflict resolution.
adacosdevGenerate conventional git commits by analyzing diffs and staging changes.
