commit

Creates git commits with auto-generated messages and optional push.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the error-prone process of preparing and recording repository changes by helping you inspect diffs, stage relevant files, and compose clear, standardized commit messages so history is meaningful and reproducible.

Core Features & Use Cases

  • Diff-aware message generation: Analyze the change summary to produce an auto-generated, type-prefixed commit message when requested.
  • Selective staging: Prefer specific file staging over bulk adds to keep commits focused.
  • Commit taxonomy & workflows: Enforce commit type conventions (feat, fix, docs, refactor, data, style) and display the resulting commit hash and summary.
  • Push control: Show the commit and always ask for confirmation before pushing; accommodate non-git workflows by detecting repository presence and noting Dropbox synchronization.
  • Use Case: Use this Skill after editing a paper chapter or analysis script to create a concise commit like "feat: add lit review bibliography" and optionally push to the remote repository.

Quick Start

Stage the edited files and create a descriptive commit by invoking the commit skill with your message or with 'auto' to generate one from the diff.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I auto-generate descriptive git commit messages from staged diffs?

You can auto-generate a commit message by invoking the commit Skill with 'auto', which inspects your git diff and status to produce a type-prefixed message following conventions like feat, fix, docs, or refactor.

Can I selectively stage files instead of using git add -A?

Yes, you can selectively stage files. The Skill prefers specific file staging over bulk adds to keep your commits focused, inspecting git status to stage only the specified files before committing changes to your repository.

Does the commit Skill work without a remote repository or pushing?

Yes, the Skill works with local repositories by detecting repository presence and returning a commit hash. It always asks for confirmation before pushing to a remote, and can even note Dropbox synchronization for non-git workflows.

What commit message conventions does this Skill enforce for version control?

The Skill enforces a commit taxonomy using type prefixes such as feat, fix, docs, refactor, data, and style. This standardized format ensures your version-control history remains meaningful and reproducible across development workflows.

Do I need a Bash environment to run git commit automation?

Yes, you need a Bash-capable environment with repository write access to run this automation. The Skill relies on Bash to inspect git status and diffs, stage files, execute commits, and optionally push changes.

Why should I use selective staging for git commits?

Selective staging keeps commits focused and history meaningful by staging only relevant files instead of bulk adding. This approach, combined with diff-aware message generation, produces reproducible version-control records.