تشغيل أي مهارة في Manus بنقرة واحدة

ابدأ الآن

commit

النجوم١٧

التفرعات٢

آخر تحديث١٩ فبراير ٢٠٢٦ في ١٥:١٨

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

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

ZacharyZhang-NY

ZacharyZhang-NY/AemeathCLI

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

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

ZacharyZhang-NY/AemeathCLI

Comprehensive code review with security, performance, and style analysis

2026-02-1917

debug

ZacharyZhang-NY/AemeathCLI

Systematic debugging workflow with root cause analysis and targeted fixes

2026-02-1917

plan

ZacharyZhang-NY/AemeathCLI

Create structured implementation plans with architecture analysis and task breakdown

2026-02-1917

refactor

ZacharyZhang-NY/AemeathCLI

Safe code refactoring with behavior preservation, test verification, and incremental steps

2026-02-1917

test

ZacharyZhang-NY/AemeathCLI

Generate comprehensive test suites with unit, integration, and edge case coverage

2026-02-1917

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.