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

commit

スター0

フォーク0

更新日2026年4月25日 09:34

Analyze staged git changes and create one or more well-scoped commits. Use when the user asks to commit, split staged changes into logical commits, or requests `/commit`-style smart committing, including single-commit mode.

インストール

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

Manusで実行

ソース

EATSTEAK

EATSTEAK/dotagents

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

ダウンロード

Manusで実行

Smart Staged Commit

Use this workflow when the user wants staged changes committed.

Arguments

--single or -s: commit all staged changes as one commit.
No argument: analyze staged changes and split them into logical commits when useful.

Workflow

Inspect staged files with git diff --cached --name-status.
If nothing is staged, show git status and stop without creating an empty commit.
Review the full staged diff with git diff --cached.
Check recent commit style with git log --oneline -20.
Classify changes by intent: feat, fix, refactor, docs, test, style, or chore.
Group changes by feature, module, dependency, and reviewability.
Before committing, show the user a concise commit plan and ask for confirmation unless the surrounding agent instructions explicitly allow committing without another confirmation.
Commit each group in dependency order.

Grouping Rules

Prefer feature-level groups when one feature spans multiple files.
Keep implementation and directly related tests together.
Keep unrelated documentation, formatting, and configuration changes separate when that improves reviewability.
Avoid overly tiny commits that do not stand on their own.
Avoid overly broad commits that mix unrelated behavior changes.

Message Format

Use the repository's existing style. If there is no stronger local convention, use Conventional Commits:

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

<body>

Keep the subject concise, lowercase, and without a trailing period.
Add a body only when it explains important context or motivation.

Single Commit Mode

When --single or -s is requested:

Analyze all staged changes together.
Draft one message that covers the full intent.
Create one commit after confirmation.

Safety

Do not commit files that likely contain secrets, credentials, or local-only configuration.
Do not amend, force-push, reset hard, or discard changes unless explicitly requested.
If a hook fails, fix the issue and create a new commit rather than amending a failed attempt.

このリポジトリの他の Skills

同じリポジトリ

pdftomd

EATSTEAK/dotagents

Convert PDF files to Markdown while preserving content accuracy and document structure. Use when the user asks for `/pdftomd`, PDF to Markdown conversion, or wants a PDF transformed into one or more Markdown files.

2026-04-250

EATSTEAK/dotagents

Prepare and create a GitHub pull request from the current branch. Use when the user asks to open a PR, create a pull request, or requests `/pr`, including an optional base branch argument.

2026-04-250

rearrange

EATSTEAK/dotagents

Analyze and reorganize current branch commits for easier review. Use when the user asks to rearrange, reorder, split, squash, or clean up commits, or requests `/rearrange` with an optional base branch.

2026-04-250

review

EATSTEAK/dotagents

Perform a code review for a branch diff, staged diff, or specific file. Use when the user asks for review, code review, `/review`, staged review, branch review, or review of a named file.

2026-04-250

summary

EATSTEAK/dotagents

Summarize current branch changes against a base branch. Use when the user asks for a branch summary, change summary, release-style summary, or `/summary` with an optional base branch.

2026-04-250

find-skills

EATSTEAK/dotagents

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

2026-02-160

Smart Staged Commit

Use this workflow when the user wants staged changes committed.

Arguments

--single or -s: commit all staged changes as one commit.

No argument: analyze staged changes and split them into logical commits when useful.

Workflow

Inspect staged files with git diff --cached --name-status.

If nothing is staged, show git status and stop without creating an empty commit.

Review the full staged diff with git diff --cached.

Check recent commit style with git log --oneline -20.

Classify changes by intent: feat, fix, refactor, docs, test, style, or chore.

Group changes by feature, module, dependency, and reviewability.

Before committing, show the user a concise commit plan and ask for confirmation unless the surrounding agent instructions explicitly allow committing without another confirmation.

Commit each group in dependency order.

Grouping Rules

Prefer feature-level groups when one feature spans multiple files.

Keep implementation and directly related tests together.

Keep unrelated documentation, formatting, and configuration changes separate when that improves reviewability.

Avoid overly tiny commits that do not stand on their own.

Avoid overly broad commits that mix unrelated behavior changes.

Message Format

Use the repository's existing style. If there is no stronger local convention, use Conventional Commits:

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

Keep the subject concise, lowercase, and without a trailing period.

Add a body only when it explains important context or motivation.

Single Commit Mode

When --single or -s is requested:

Analyze all staged changes together.

Draft one message that covers the full intent.

Create one commit after confirmation.

Safety

Do not commit files that likely contain secrets, credentials, or local-only configuration.

Do not amend, force-push, reset hard, or discard changes unless explicitly requested.

If a hook fails, fix the issue and create a new commit rather than amending a failed attempt.

name	commit
description	Analyze staged git changes and create one or more well-scoped commits. Use when the user asks to commit, split staged changes into logical commits, or requests `/commit`-style smart committing, including single-commit mode.