commit

Verify staged Git changes and compose a conventional commit message.

10|5|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/JHostalek/dotclaude --skill commit-jhostalek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/JHostalek/dotclaude/tree/main/skills/commit
Command: npx skills add https://github.com/JHostalek/dotclaude --skill commit-jhostalek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents accidental or poorly scoped Git commits by verifying the staged changes, branch context, and commit message intent before authorizing a commit.

Core Features & Use Cases

  • Staged Set Verification: Compare staged changes with the full worktree to detect unexpected index residue or incomplete staging.
  • Branch Safety Checks: Identify changes that appear inconsistent with the current branch and request confirmation before committing.
  • Conventional Commit Guidance: Load the repository's commit conventions and produce a focused message that captures intent.
  • Use Case: When several files contain mixed feature and cleanup changes, use this Skill to inspect the staged set, confirm the branch is appropriate, and create a precise commit.

Quick Start

Ask the commit skill to review the staged changes and create an appropriate conventional commit.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I verify staged Git changes before committing to avoid accidental commits?

Yes, conventional commit guidance loads your repository's specific commit conventions and produces a focused message that captures intent. This ensures commit messages adhere to your project's established formatting and semantic standards.

What is the best way to check branch consistency before creating a Git commit?

Branch consistency checks identify changes that appear inconsistent with the current branch and request confirmation before committing. This validation prevents mixing unrelated feature and cleanup changes on incorrect branches.

Can I create a conventional commit message for mixed feature and cleanup changes?

Yes, conventional commit guidance loads your repository's specific commit conventions and produces a focused message that captures intent. This ensures commit messages adhere to your project's established formatting and semantic standards.

How do I handle Git index residue or incomplete staging before a commit?

Handle index residue by inspecting the staged set and comparing it with the full worktree to detect incomplete staging. This process ensures only the intended modifications are authorized for the final commit.

When should I inspect my staged set instead of committing all worktree changes directly?

Inspect the staged set when your worktree contains mixed changes, such as combined feature and cleanup edits. Comparing staged files against the full worktree prevents accidental commits and ensures branch consistency.

Do I need to manually clean up after Git commit hooks or partial staging?

Cleanup after commit hooks or partial staging is handled by verifying the staged set and worktree comparison. This ensures no unexpected index residue remains and the branch context stays consistent after committing.