skills.rest
kkhys
kkhysCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

formatting-commit

Guide developers in applying commit strategies and conventional commit formatting.

1|Updated Jan 10, 2026
Search Tags:#git#commit#squash#version-control#conventional-commits#interactive-rebase
One-click install
npx skills add https://github.com/kkhys/claude-code-marketplace --skill formatting-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: formatting-commit
Source: https://github.com/kkhys/claude-code-marketplace/tree/main/plugins/base/skills/formatting-commit
Command: npx skills add https://github.com/kkhys/claude-code-marketplace --skill formatting-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Commits code changes with a clear strategy and meaningful messages, ensuring a maintainable git history.

Core Features & Use Cases

  • Default Squash: Consolidate related changes into a single, coherent commit.
  • New Commit & Interactive Rebase: Create independent commits or reorganize history to reflect logical steps.
  • Conventional Commits: Enforce a standardized message format to improve traceability and automation.

Quick Start

Describe and apply the appropriate commit strategy for your current changes.

Frequently Asked Questions about formatting-commit

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

FAQPage Schema
What is the best way to squash commits and write conventional commit messages?▼

Squashing commits consolidates related changes into a single coherent git commit, while conventional commits enforce a standardized message format for traceability. This strategy maintains a clean, meaningful git history.

How do I use interactive rebase to reorganize my git history?▼

Use interactive rebase to reorganize git history into logical steps. This commit strategy allows you to create independent commits or consolidate changes, providing an alternative to the default squash approach.

When do I need conventional commits in version control?▼

You need conventional commits in version control to enforce a standardized message format across feature development and bug fixes. This formatting improves project traceability and supports automation within your git history.

Does this commit formatting strategy work for both bug fixes and feature development?▼

Yes, this commit formatting strategy applies to bug fixes, feature development, and maintenance tasks. It supports multiple commit strategies including squash, new commits, and interactive rebase across any software project.

How do I create an independent new commit instead of squashing my changes?▼

Select the new commit strategy to create independent commits instead of squashing. This preserves your changes as separate logical steps within your git history, offering an alternative to consolidating related changes.

Why should I enforce a standardized git commit message format?▼

Enforcing a standardized git commit message format ensures a maintainable history and improves project traceability. Conventional commits clarify the purpose of code changes across feature development, bug fixes, and maintenance.

Related Skills

Explore More Software Engineering Skills→
CivicActionsCivicActions
2

organize-commits

Group unstaged changes into atomic git commits using project conventions.

Official
Intermediate
t0labt0lab
2

release

Analyze Conventional Commits to draft changelogs and create release commits and tags.

Official
Advanced
OnClickListener2048OnClickListener2048

chinese-commit-conventions

Enforce Chinese commit conventions and generate changelogs from Git history.

Community
Intermediate
linuxfoundationlinuxfoundation
3.4k

dco

Recover unsigned commits by applying DCO sign-offs via amend, rebase, or cherry-pick.

Official
Advanced