ワンクリックでManusで任意のスキルを実行

git-smart-commit

スター2

フォーク1

更新日2026年4月2日 22:41

Generate intelligent conventional commit messages from staged changes. Analyzes diffs, auto-detects scope and breaking changes, and commits with approval.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

xmqywx

xmqywx/claude-code-skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Git Smart Commit

Generate a precise conventional commit message from the currently staged changes, then commit after user approval.

Steps

1. Gather Context

Run these commands to understand the staged changes and recent commit style:

git diff --cached --stat
git diff --cached
git log --oneline -10

If there are no staged changes, inform the user and suggest they stage files first (git add <files>). Do not proceed with an empty diff.

2. Analyze the Diff

Examine every file in the staged diff. Determine:

What changed: New files, modified logic, deleted code, config changes, dependency updates.
Why it changed: Infer intent from the nature of the change (new feature, bug fix, refactor, etc.).
Scope: Derive scope from the file paths. Use the most specific meaningful directory or module name.
- src/auth/login.ts -> scope is auth
- tests/utils/parser.test.js -> scope is utils
- package.json only -> scope is deps
- .github/workflows/ci.yml -> scope is ci
- Multiple unrelated scopes -> omit scope or use the dominant one.
Breaking changes: Look for removed public APIs, renamed exports, changed function signatures, deleted fields, major dependency version bumps, or migration-requiring config changes.

3. Select Commit Type

Choose exactly one type based on priority:

Type	When to use
`feat`	New feature or capability added
`fix`	Bug fix or correction
`docs`	Documentation only changes
`refactor`	Code restructuring with no behavior change
`perf`	Performance improvement
`test`	Adding or updating tests
`ci`	CI/CD pipeline changes
`build`	Build system or dependency changes
`chore`	Maintenance tasks, tooling, config
`style`	Formatting, whitespace, semicolons (no logic change)
`revert`	Reverting a previous commit

4. Compose the Commit Message

Follow this structure:

<type>(<scope>): <subject>

<body>

<footer>

Rules:

Subject line: imperative mood, lowercase, no period, max 72 characters.
Body (optional): Explain what and why, not how. Wrap at 80 characters. Include only if the subject alone is insufficient.
Footer: Add BREAKING CHANGE: <description> if breaking changes were detected. Reference issue numbers if visible in branch name or diff comments (e.g., Closes #42).

5. Present for Approval

Show the complete commit message to the user in a fenced code block. Ask:

Ready to commit with this message? (yes / edit / abort)

If yes: Run git commit -m "<message>" using a HEREDOC for multi-line messages.
If edit: Ask the user what to change, revise, and re-present.
If abort: Stop without committing.

6. Confirm

After committing, run git log --oneline -1 to confirm the commit was created and display the short hash and message.

Edge Cases

Merge commits: Note that the staged changes are part of a merge and keep the message descriptive of the merge resolution.
Large diffs (>500 lines): Summarize by file group rather than reading every line. Focus on the overall intent.
Mixed concerns: If staged changes span multiple unrelated concerns, recommend the user split them into separate commits. Offer to help unstage files.
Amend requests: If the user says "amend", use git commit --amend but warn that this rewrites history.

このリポジトリの他の Skills

同じリポジトリ

agent-sdk-builder

xmqywx/claude-code-skills

Build production AI agents using Anthropic's Claude Agent SDK (TypeScript or Python). Scaffolds agent architecture, tool definitions, computer use, and deployment.

2026-04-022

api-scaffold

xmqywx/claude-code-skills

Scaffold a production-ready REST API endpoint with CRUD operations, input validation, error handling, rate limiting, and test skeletons. Supports Express and Fastify.

2026-04-022

code-review

xmqywx/claude-code-skills

Perform an automated code review on recent changes. Checks for security issues, performance problems, error handling gaps, and code quality. Outputs a structured report with severity levels.

2026-04-022

content-pipeline-architect

xmqywx/claude-code-skills

Design and build automated content production pipelines. Takes a topic, brand voice, and target platforms, then generates a complete content calendar, platform-optimized posts, and an automation workflow plan. Ideal for social media, YouTube, blogs, and newsletters.

2026-04-022

customer-service-automation

xmqywx/claude-code-skills

Design AI-powered customer service automation systems. Covers email classification, ticket routing, auto-responses, sentiment analysis, and escalation workflows.

2026-04-022

data-extraction-engine

xmqywx/claude-code-skills

Extract structured data from any source — websites, PDFs, APIs, emails, documents. Generate extraction scripts, parsers, and data pipelines.

2026-04-022

name	git-smart-commit
description	Generate intelligent conventional commit messages from staged changes. Analyzes diffs, auto-detects scope and breaking changes, and commits with approval.

Git Smart Commit

Generate a precise conventional commit message from the currently staged changes, then commit after user approval.

Steps

1. Gather Context

Run these commands to understand the staged changes and recent commit style:

git diff --cached --stat
git diff --cached
git log --oneline -10

If there are no staged changes, inform the user and suggest they stage files first (git add <files>). Do not proceed with an empty diff.

2. Analyze the Diff

Examine every file in the staged diff. Determine:

What changed: New files, modified logic, deleted code, config changes, dependency updates.
Why it changed: Infer intent from the nature of the change (new feature, bug fix, refactor, etc.).
Scope: Derive scope from the file paths. Use the most specific meaningful directory or module name.
- src/auth/login.ts -> scope is auth
- tests/utils/parser.test.js -> scope is utils
- package.json only -> scope is deps
- .github/workflows/ci.yml -> scope is ci
- Multiple unrelated scopes -> omit scope or use the dominant one.
Breaking changes: Look for removed public APIs, renamed exports, changed function signatures, deleted fields, major dependency version bumps, or migration-requiring config changes.

3. Select Commit Type

Choose exactly one type based on priority:

Type	When to use
`feat`	New feature or capability added
`fix`	Bug fix or correction
`docs`	Documentation only changes
`refactor`	Code restructuring with no behavior change
`perf`	Performance improvement
`test`	Adding or updating tests
`ci`	CI/CD pipeline changes
`build`	Build system or dependency changes
`chore`	Maintenance tasks, tooling, config
`style`	Formatting, whitespace, semicolons (no logic change)
`revert`	Reverting a previous commit

4. Compose the Commit Message

Follow this structure:

<type>(<scope>): <subject>

<body>

<footer>

Rules:

Subject line: imperative mood, lowercase, no period, max 72 characters.
Body (optional): Explain what and why, not how. Wrap at 80 characters. Include only if the subject alone is insufficient.
Footer: Add BREAKING CHANGE: <description> if breaking changes were detected. Reference issue numbers if visible in branch name or diff comments (e.g., Closes #42).

5. Present for Approval

Show the complete commit message to the user in a fenced code block. Ask:

Ready to commit with this message? (yes / edit / abort)

If yes: Run git commit -m "<message>" using a HEREDOC for multi-line messages.
If edit: Ask the user what to change, revise, and re-present.
If abort: Stop without committing.

6. Confirm

After committing, run git log --oneline -1 to confirm the commit was created and display the short hash and message.

Edge Cases

Merge commits: Note that the staged changes are part of a merge and keep the message descriptive of the merge resolution.
Large diffs (>500 lines): Summarize by file group rather than reading every line. Focus on the overall intent.
Mixed concerns: If staged changes span multiple unrelated concerns, recommend the user split them into separate commits. Offer to help unstage files.
Amend requests: If the user says "amend", use git commit --amend but warn that this rewrites history.