Generate imperative git commit messages from staged changes.
npx skills add https://github.com/schirrmacher/coding --skill commit-name
Please help me install this Agent Skill. Skill: commit-name Source: https://github.com/schirrmacher/coding/tree/main/skills/commit-name Command: npx skills add https://github.com/schirrmacher/coding --skill commit-name
Writing clear, concise commit messages is tedious and error-prone; this Skill generates an imperative, easy-to-read subject that describes the change and a brief body with non-obvious details when needed.
Run the tool after staging changes to generate a concise commit message.
High-intent search queries and answers about installing and using this skill.
To automatically generate a git commit message from staged changes, use this tool after staging your files. It analyzes the staged diff to produce a concise, imperative subject line and optional body bullets for non-obvious details.
An imperative commit message subject line should be lowercase, max 50 characters, and end without a period. This tool automatically formats the generated subject from your staged diff to fulfill these specific constraints.
Yes, you can generate commit messages for both code and documentation updates. The tool works across typical project changes, including code, config, and docs, to create appropriate subjects and body explanations.
To add bullet points to a commit message body for non-obvious changes, the tool optionally produces up to three bullets. Each generated bullet is constrained to 80 characters to explain non-obvious details from the staged diff.
The best way to write concise git commit messages from a diff is to automate the process. This tool reads the staged diff and generates a short, imperative subject with optional body bullets, avoiding tedious and error-prone manual writing.
ss49919201Stage git changes and generate commit messages from diffs.
mattg101Stage all changes, commit with a message, and push to a remote Git repository.
SocketDevCreate, review, and prune Git worktrees for pull request workflows.
trevin-jRun tests, linters, and static analysis before committing with Conventional Commits.
