How do I install the Formatting Commits skill?

Run npx skillmds@latest add lijinnair/formatting-commits in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Formatting Commits safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Formatting Commits?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Formatting Commits free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Formatting Commits?

lijinnair (@lijinnair) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Formatting Commits by lijinnair — Agent Skill

Name: Formatting Commits
Author: lijinnair

Formatting Commits

Generates a well-structured, conventional Git commit message from the user's staged changes or a description of what they did. Use when the user says "write a commit message", "format my commit", or "help me commit this". Outputs a ready-to-paste commit message following the Conventional Commits specification.

lijinnair 74986a8 2.0 KB Updated Sep 17, 2026

File contents

Git Commit Formatting SOP

Execution Steps

Step 1: Gather Staged Changes

If the user has not provided a description, run:

!`git diff --staged`

to capture the actual code changes as context.

Step 2: Classify the Change Type

Determine the correct Conventional Commits type based on the diff or description:

feat — A new feature
fix — A bug fix
docs — Documentation only changes
style — Formatting, missing semi-colons, etc.
refactor — Code change that is neither a fix nor a feature
chore — Build process, dependency updates
test — Adding or fixing tests

Step 3: Extract Scope

Identify the affected module, component, or file area (e.g., auth, api, ui). Use (scope) in the commit header.

Step 4: Write the Commit Message

Compose the full commit message following this structure:

<type>(<scope>): <short imperative summary under 72 chars>

<optional body: what changed and why, not how>

<optional footer: BREAKING CHANGE: ... or Closes #issue>

Examples:

Input: Added user authentication with JWT tokens Output:

feat(auth): implement JWT-based authentication

Add login endpoint and token validation middleware

Input: Fixed bug where dates displayed incorrectly in reports Output:

fix(reports): correct date formatting in timezone conversion

Use UTC timestamps consistently across report generation

Input: Updated dependencies and refactored error handling Output:

chore: update dependencies and refactor error handling

- Upgrade lodash to 4.17.21
- Standardize error response format across endpoints

Step 5: Deliver

Output the final commit message in a single code block, ready to copy-paste into the terminal.

---name: formatting-commitsdescription: Generates a well-structured, conventional Git commit message from the user's staged changes or a description of what they did. Use when the user says "write a commit message", "format my commit", or "help me commit this". Outputs a ready-to-paste commit message following the Conventional Commits specification.---# Git Commit Formatting SOP## Execution Steps### Step 1: Gather Staged ChangesIf the user has not provided a description, run:```!`git diff --staged````to capture the actual code changes as context.### Step 2: Classify the Change TypeDetermine the correct Conventional Commits type based on the diff or description:- `feat` — A new feature- `fix` — A bug fix- `docs` — Documentation only changes- `style` — Formatting, missing semi-colons, etc.- `refactor` — Code change that is neither a fix nor a feature- `chore` — Build process, dependency updates- `test` — Adding or fixing tests### Step 3: Extract ScopeIdentify the affected module, component, or file area (e.g., `auth`, `api`, `ui`). Use `(scope)` in the commit header.### Step 4: Write the Commit MessageCompose the full commit message following this structure:```<type>(<scope>): <short imperative summary under 72 chars><optional body: what changed and why, not how><optional footer: BREAKING CHANGE: ... or Closes #issue>```**Examples:**Input: Added user authentication with JWT tokensOutput:```feat(auth): implement JWT-based authenticationAdd login endpoint and token validation middleware```Input: Fixed bug where dates displayed incorrectly in reportsOutput:```fix(reports): correct date formatting in timezone conversionUse UTC timestamps consistently across report generation```Input: Updated dependencies and refactored error handlingOutput:```chore: update dependencies and refactor error handling- Upgrade lodash to 4.17.21- Standardize error response format across endpoints```### Step 5: DeliverOutput the final commit message in a single code block, ready to copy-paste into the terminal.

Frequently asked questions