commit

Create Conventional Commits with staging, scope detection, amend, and fixup workflows.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/dotBeeps/hoard --skill commit-dotbeeps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/dotBeeps/hoard/tree/main/morsels/skills/commit
Command: npx skills add https://github.com/dotBeeps/hoard --skill commit-dotbeeps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create clear, consistent, and convention-compliant git commit messages while handling staging, scope detection, amending, and fixup workflows so commits are ready for review and history hygiene.

Core Features & Use Cases

  • Conventional Commit Formatting: Enforces type(scope): summary style and recommends bodies when context is needed.
  • Staging and Scope Detection: Stages specified files or hunks, detects scope from recent messages and repo structure, and asks when ambiguous files are present.
  • Amend & Fixup Support: Guides safe --amend usage with pushed-commit warnings and creates fixup commits for later autosquash during interactive rebase.
  • Use Case: Turn a mixed-change working tree into a single, well-scoped commit or create a fixup for an earlier change before rebasing.

Quick Start

Use the commit skill to stage my changed files and create a Conventional Commit like fix(auth): handle expired SSH keys gracefully.

Frequently Asked Questions about commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create conventional commits for staged and unstaged git changes?

To create conventional commits, this skill stages specified files or hunks and formats messages into the type(scope): summary style. It detects scope from recent repo history and recommends commit bodies when additional context is needed.

What is the best way to amend a git commit that has already been pushed?

When you amend a pushed git commit, this skill warns you about the potential history conflicts. It guides safe --amend usage by detecting previously pushed commits and preventing unsafe history rewrites.

How do I create a fixup commit for an interactive rebase?

You create a fixup commit by instructing this skill to target an earlier change. It generates a fixup commit automatically, which you can later autosquash during an interactive rebase to maintain history hygiene.

How does scope detection work for conventional commit messages?

Scope detection works by analyzing recent commit messages and your repository structure. When ambiguous files are present, the skill asks you to clarify the scope before formatting the final conventional commit message.

Can I stage specific file hunks before generating a conventional commit?

Yes, you can stage specific file hunks before generating a conventional commit. The skill handles staging individual hunks or files, converting a mixed-change working tree into a single, well-scoped commit.

When should I use fixup commits instead of amending my last commit?

Use fixup commits to correct older history entries during an interactive rebase, while amending targets only the most recent commit. The skill provides warnings when attempting to amend commits that are already pushed to a remote.