commit

Commit staged changes with a formatted message using git best practices.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commits staged changes with an appropriate commit message using the git-operations-specialist skill.

Core Features & Use Cases

  • Check Staging Status: Run git status to confirm what changes are staged.
  • Review Staged Changes: Use git diff --staged to review the content of staged changes.
  • Create Commit: Commit the staged changes with an appropriate commit message.
  • Verify Commit: Run git status after committing to confirm the commit was successful.
  • Commit Message Guidelines: Follow the .gitmessage template format and use prefixes like feat, fix, refactor, docs, style, test, chore.
  • Constraints: Never use git add, perform a single commit for all staged changes; use HEREDOC for commit messages.
  • Example: If you have staged files, commit with a message like feat: タイムラインAPIのルートと型定義を追加.

Quick Start

Review the staged changes and trigger the commit operation to create a single, properly formatted commit.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I commit staged changes with a structured git message?

To commit staged changes with a structured git message, the skill checks staging status, reviews the staged diff, and applies a formatted commit using prefixes like feat, fix, or refactor based on best practices.

What is the best way to ensure a single, well-formed git commit per batch?

The best way to ensure a single, well-formed git commit is to automate the process using HEREDOC for multi-line messages and strictly avoid using git add, guaranteeing only currently staged files are committed.

Does this commit workflow automatically stage unstaged files before committing?

No, this commit workflow does not automatically stage files. It explicitly avoids using git add and operates solely on currently staged changes to ensure you commit exactly what you intended.

What git commit message prefixes should I use for version control best practices?

For version control best practices, you should use standard prefixes defined in the .gitmessage template, including feat, fix, refactor, docs, style, test, and chore to categorize your changes.

How do I verify a git commit was successful after applying staged changes?

To verify a git commit was successful, the workflow runs git status immediately after creating the commit to confirm the changes were applied and the working tree is clean.

Can I use this approach to review staged content before finalizing a git commit?

Yes, you can review staged content before finalizing a git commit because the process explicitly runs git diff --staged to inspect the exact modifications prior to generating the commit message.