commit

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

跳到安装

仓库: ZacharyZhang-NY/AemeathCLI
最近来源活动: 2026年2月19日 15:18
检测到的 SKILL.md 语言: 英语
星标: 17
分支: 2

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

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

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

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.

返回搜索返回安装

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

查看这个仓库的全部 Skills

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

来源信息

安装方式

检查来源文件

Commit Skill

Process

Step 1 — Analyze Changes

Step 2 — Categorize Changes

Step 3 — Safety Checks

Step 4 — Draft Commit Message

Step 5 — Execute

Rules

同仓库更多 Skills

Commit Skill

Process

Step 1 — Analyze Changes

Step 2 — Categorize Changes

Step 3 — Safety Checks

Step 4 — Draft Commit Message

Step 5 — Execute

Rules

同仓库更多 Skills