committing

Name: committing
Availability: InStock
Author: missingbulb

Enforces one-concern-per-commit discipline with issue references and explicit file staging in git.

Updated Jun 12, 2026

Search Tags:#git #workflow #code review #version control #commit #staging #issue tracking

Ready to run

npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill committing-missingbulb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: committing
Source: https://github.com/missingbulb/GoogleCalendarEventCreator/tree/main/.claudinite/shared/packs/basics/skills/committing
Command: npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill committing-missingbulb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents messy git history caused by mixed-concern commits, missing issue references, and accidental staging of unrelated changes. ## Core Features & Use Cases - Single-Concern Commits: Splits changes so each commit stands alone, avoiding messages that need numbered lists. - Issue Referencing: Adds Refs, Fixes, or Closes references so commits trace back to tracked work. - Named Staging: Stages files explicitly with git add <paths> instead of sweeping everything with -a. - Use Case: Before committing a bug fix plus an unrelated refactor, split them into two commits, each referencing its own issue. ## Quick Start Ask the assistant to commit the current changes following the committing guidelines before running any git commit.

Frequently Asked Questions about committing

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

FAQPage Schema

How do I write a good git commit message?▼

Keep each commit to a single concern so the message describes one change. Reference the related issue with Refs #n, or Fixes #n when the commit completes the work.

How to split mixed changes into separate git commits?▼

Stage files by name with git add <paths> for each logical change, then commit each group separately. If your message wants numbered items, that signals the commit should be split.

Should I use git commit -a to stage all changes?▼

No, git commit -a sweeps in unrelated work in progress. Stage files explicitly by name with git add <paths> so each commit contains only the files it is about.

How do I fix a commit that is already pushed?▼

A landed commit is revised by creating a new commit, never by rewriting the original one. This keeps shared history intact for collaborators.

When should a commit reference an issue number?▼

Reference the issue whenever the change is tracked by one, using Refs #n for related work or Fixes #n and Closes #n when the commit finishes it. Changes tracked only by a PR reference nothing.