agentsclimarketplace

Commit

Skill dceoy/ai-coding-agent-skills/skills/commit

Agent skills for AI coders

Install
npx -y skills add dceoy/ai-coding-agent-skills --skill commit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create a single git commit from current staged and unstaged changes with an appropriate message. Use when the user asks to commit current work.

SKILL.md

2.0 KB, as published. Nobody here has run it

Commit Skill

Stage and commit current changes with a concise, well-formed commit message based on the diff and recent commit history.

When to Use

  • After completing a change and wanting to commit it.
  • When all modifications are ready to be captured in a single commit.

Agent Compatibility

This skill is tool-agnostic and can be executed by Claude Code, Codex CLI, or Cursor CLI.

Inputs

  • Current repository with uncommitted changes (staged or unstaged).

If there are no changes to commit, report that and stop.

Do not stage or commit unrelated user changes unless the user explicitly asked to include them.

Workflow

  1. Gather context by running these commands in parallel:

    git status
    git diff HEAD
    git branch --show-current
    git log --oneline -10
    
  2. Analyze changes from the diff output to understand what was modified and why. If the diff contains unrelated changes, include only the files that belong to the requested work.

  3. Stage relevant files using git add for the appropriate files. Prefer explicit paths over git add . when the worktree contains unrelated changes.

  4. Create a commit with a concise, descriptive message that:

    • Follows the repository's existing commit message style (based on recent commits).
    • Summarizes the nature of the change (new feature, bug fix, refactor, etc.).
    • Uses imperative mood and sentence case.

Stage and commit should be executed as efficiently as possible once the relevant scope is clear.

Do not perform extra cleanup, formatting, tests, branch changes, pushes, or PR creation unless requested separately.

Outputs

  • A new git commit on the current branch.
  • Console output confirming the commit was created.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.