at-commit

Featured

Generate a Conventional Commits message from staged changes and wait for confirmation before committing. Use when the user asks to commit or generate a commit message.

Code & Development 179 stars 0 forks Updated yesterday MIT

Install

Quality Score: 91/100

Stars 20%

75

Recency 20%

100

Frontmatter 20%

70

Documentation 15%

100

Issue Health 10%

50

License 10%

100

Description 5%

100

Skill Content

# Commit Message Generator ## Workflow 1. Run `git diff --staged` to inspect staged changes. If it is empty, tell the user to run `git add` first and stop. 2. Determine the description language using the Language Policy below. 3. Generate the message(s) and show them for confirmation; do not commit immediately. When more than one framing is reasonable, present them as a short numbered list (`1)`, `2)`, …) so the user can pick by replying with just the number. A single clear message may be shown on its own. The user may also reply with an edit or their own wording. 4. Run `git commit -m` only after the user picks or explicitly confirms — a number from the list, "commit", or "ok" all count. Do not run `git push` unless the user explicitly asks. ## Language Policy Use this priority order for the human-readable description after `type(scope):`: 1. Use the language explicitly requested by the user in this turn. 2. Otherwise use the repository preference in `.agent-tools/config.jsonc`, if it defines `at-commit.language`. 3. Otherwise use the global preference in `~/.agent-tools/config.jsonc`, if it defines `at-commit.language`. 4. Otherwise use the language of the user's actual invocation text when it contains a clear, independent natural-language request. Ignore injected skill instructions, quoted or pasted content, code blocks, diffs, and tool output. 5. Otherwise match the dominant language in recent repository commit subjects. 6. If no dominant language is clear, default t...

Details

Author: kairyou
Repository: kairyou/agent-tools
Created: 2 months ago
Last Updated: yesterday
Language: JavaScript
License: MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

generate-commit-message

Generate, revise, or validate English Conventional Commit messages from Git repository changes, diffs, patches, file lists, or user-provided change summaries. Use when asked to draft a commit message, choose a commit type or scope, describe staged or unstaged work, or add a breaking-change or issue footer. Inspect all uncommitted changes by default, return a single commit message covering the whole change set unless the user explicitly asks for a split, and never stage files or create the commit.

0 Updated 2 weeks ago

Code & Development Listed

commit-message

Use ANY time the user signals they want to commit staged changes — including bare "commit", "/commit", "commit this", "commit these changes", "let's commit", "make a commit", "git commit", "write a commit message", "make a conventional commit", "use conventional commits", or any equivalent phrasing in context (e.g., right after staging files, "ready to commit", "okay ship it"). Composes a Conventional Commits message with a gitmoji prefix: reads the staged diff, decides type, scope, emoji, subject, body, and footer using the rubrics in this file, shows one assembled message in a fenced block, and commits after a single yes/no confirmation. It writes the commit message only — NOT other prose about the staged changes: not PR/MR descriptions, not release notes, not changelogs or summaries. Also do NOT use for questions *about* git or *about* conventional commits, amending, rebasing, cherry-picking, reverting/undoing commits, or viewing log history.

5 Updated yesterday

Code & Development Listed

commit

Generate a Conventional Commits message from the staged diff and create the commit after user confirmation. TRIGGER when the user says "commit these changes", "commit this", "generate a commit message", "stage and commit", "commit with CC", "write a commit message", "summarize my diff into a commit", "/nyann:commit". Do NOT trigger on "git commit" in an informational context or when the user is just asking what a commit message means. DISAMBIGUATION: if the user mentions BOTH branch creation AND committing in the same message (e.g. "start a branch and commit this", "new branch + commit"), route to the `new-branch` skill FIRST; `commit` will take over after the branch is created. When nothing is staged, guide the user to stage first rather than silently staging everything.

6 Updated 1 weeks ago