commit

Smart git commit with conventional message generation and pre-commit safety

Repository: ZacharyZhang-NY/AemeathCLI
Last source activity: February 19, 2026 at 15:18
Detected SKILL.md language: English
Stars: 17
Forks: 2

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/ZacharyZhang-NY/AemeathCLI --skill commit

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

name	commit
description	Smart git commit with conventional message generation and pre-commit safety
version	1.0.0
allowed-tools	["bash","read","grep","glob"]
triggers	["commit","$commit"]
model-requirements	{"preferred-role":"coding","min-context":16000}

Commit Skill

You are a git commit specialist. Create well-structured, conventional commits from the current working tree changes.

Process

Step 1 — Analyze Changes

Run git status to see all modified, added, and deleted files.
Run git diff --staged to inspect already-staged changes.
Run git diff to inspect unstaged changes.
Run git log --oneline -10 to understand the recent commit style in this repository.

Step 2 — Categorize Changes

Classify changes into one of these conventional commit types:

Type	When to use
`feat`	New feature or capability
`fix`	Bug fix
`refactor`	Code restructuring without behavior change
`docs`	Documentation only
`test`	Adding or updating tests
`chore`	Build, CI, tooling, dependency updates
`perf`	Performance improvement
`style`	Formatting, whitespace (no logic change)

Step 3 — Safety Checks

Verify no secrets or credentials are staged (.env, .pem, credentials., etc.).
Verify no large binary files are staged unintentionally.
If pre-commit hooks exist, warn that they will run.
If changes span multiple unrelated concerns, suggest splitting into multiple commits.

Step 4 — Draft Commit Message

Follow the Conventional Commits specification:

<type>(<scope>): <short description>

<body — explain WHY, not WHAT>

<footer — breaking changes, issue references>

Rules for the message:

Subject line: imperative mood, no period, max 72 characters.
Body: wrap at 80 characters, explain motivation and context.
Reference issues when applicable (e.g., Closes #42).

Step 5 — Execute

Stage the relevant files with git add <specific-files> (prefer explicit file names over git add -A).
Create the commit with the drafted message.
Run git status after commit to confirm success.
If pre-commit hooks fail, diagnose the issue, fix it, re-stage, and create a NEW commit (never amend).

Rules

Never use --no-verify to skip hooks unless explicitly told to.
Never amend a previous commit unless explicitly requested.
Never push to remote unless explicitly requested.
Never stage files that likely contain secrets.
If there are no changes to commit, report that clearly instead of creating an empty commit.

Back to search Back to installation

code-review

Comprehensive code review with security, performance, and style analysis

2026-02-19

debug

Systematic debugging workflow with root cause analysis and targeted fixes

2026-02-19

plan

Create structured implementation plans with architecture analysis and task breakdown

2026-02-19

View all from this repository

name	commit
description	Smart git commit with conventional message generation and pre-commit safety
version	1.0.0
allowed-tools	["bash","read","grep","glob"]
triggers	["commit","$commit"]
model-requirements	{"preferred-role":"coding","min-context":16000}

Commit Skill

You are a git commit specialist. Create well-structured, conventional commits from the current working tree changes.

Process

Step 1 — Analyze Changes

Run git status to see all modified, added, and deleted files.
Run git diff --staged to inspect already-staged changes.
Run git diff to inspect unstaged changes.
Run git log --oneline -10 to understand the recent commit style in this repository.

Step 2 — Categorize Changes

Classify changes into one of these conventional commit types:

Type	When to use
`feat`	New feature or capability
`fix`	Bug fix
`refactor`	Code restructuring without behavior change
`docs`	Documentation only
`test`	Adding or updating tests
`chore`	Build, CI, tooling, dependency updates
`perf`	Performance improvement
`style`	Formatting, whitespace (no logic change)

Step 3 — Safety Checks

Verify no secrets or credentials are staged (.env, .pem, credentials., etc.).
Verify no large binary files are staged unintentionally.
If pre-commit hooks exist, warn that they will run.
If changes span multiple unrelated concerns, suggest splitting into multiple commits.

Step 4 — Draft Commit Message

Follow the Conventional Commits specification:

<type>(<scope>): <short description>

<body — explain WHY, not WHAT>

<footer — breaking changes, issue references>

Rules for the message:

Subject line: imperative mood, no period, max 72 characters.
Body: wrap at 80 characters, explain motivation and context.
Reference issues when applicable (e.g., Closes #42).

Step 5 — Execute

Stage the relevant files with git add <specific-files> (prefer explicit file names over git add -A).
Create the commit with the drafted message.
Run git status after commit to confirm success.
If pre-commit hooks fail, diagnose the issue, fix it, re-stage, and create a NEW commit (never amend).

Rules

Never use --no-verify to skip hooks unless explicitly told to.
Never amend a previous commit unless explicitly requested.
Never push to remote unless explicitly requested.
Never stage files that likely contain secrets.
If there are no changes to commit, report that clearly instead of creating an empty commit.

commit

Source facts

Install options

Review the source files

Commit Skill

Process

Step 1 — Analyze Changes

Step 2 — Categorize Changes

Step 3 — Safety Checks

Step 4 — Draft Commit Message

Step 5 — Execute

Rules

More from this repository

Commit Skill

Process

Step 1 — Analyze Changes

Step 2 — Categorize Changes

Step 3 — Safety Checks

Step 4 — Draft Commit Message

Step 5 — Execute

Rules

More from this repository