commit

Review repository changes and create git commits from staged and unstaged changes.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/obenland/dotfiles --skill commit-obenland
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/obenland/dotfiles/tree/main/claude/.claude/skills/commit
Command: npx skills add https://github.com/obenland/dotfiles --skill commit-obenland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the process of reviewing repository changes and creating clean, well-documented commits, saving time and reducing error-prone messages.

Core Features & Use Cases

  • Review staged and unstaged changes using git status and git diff.
  • Stage relevant files (ask if unsure what to stage).
  • Create a clear, concise commit message that describes what changed and why.
  • Follow the project's commit conventions based on recent history.
  • After committing, show the git status to confirm success.

Quick Start

Review the current repository state and create a commit with a clear, conventional message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I craft a clean git commit message from staged and unstaged changes?▼

This skill automates reviewing staged and unstaged changes via git diff and git status, then generates a clear, conventional commit message describing what changed and why to ensure well-documented git commits.

Does this git commit workflow follow my project's existing commit conventions?▼

Yes, it analyzes your repository's recent commit history to detect and adhere to project-specific commit conventions, ensuring generated commit messages match your team's established formatting standards.

What's the best way to automate code review before creating a git commit?▼

Automating code review before a git commit involves evaluating git diff and git status output, prompting for file staging confirmation, and generating a descriptive commit message to reduce error-prone manual messages.

Can I use this to stage files automatically across a large codebase?▼

Yes, it supports large codebases by reviewing staged and unstaged changes and asking for confirmation when unsure what to stage, ensuring only relevant files are included in the final git commit.

Do I need a specific git installation or configuration to review repository changes?▼

You need a working git installation and repository access to review changes and create commits; no additional dependencies or components are required beyond the standard git environment for daily development workflows.

How does this workflow handle unstaged changes when preparing a commit?▼

It reviews unstaged changes via git diff, prompts to stage relevant files when unsure, generates a concise commit message, and displays git status after committing to confirm the repository changes were applied successfully.