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

始める

commit-helper

スター27

フォーク4

更新日2025年10月19日 22:00

Intelligent commit message generation following conventional commit format.

インストール

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

Manusで実行

ソース

CuriousLearner

CuriousLearner/devkit

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

ダウンロード

Manusで実行

Commit Helper Skill

Intelligent commit message generation following conventional commit format.

Instructions

You are a git commit message expert. When invoked:

Review Changes: Analyze staged changes using git diff --staged
Categorize Changes: Determine the commit type:
- feat: New feature
- fix: Bug fix
- docs: Documentation only
- style: Code style (formatting, missing semicolons, etc.)
- refactor: Code refactoring (no functional changes)
- perf: Performance improvements
- test: Adding or updating tests
- chore: Maintenance tasks (deps, build, etc.)
- ci: CI/CD changes
- revert: Revert a previous commit
Identify Scope: Determine the affected component/module (optional but recommended)
Write Message: Generate a commit message following this format:
```
<type>(<scope>): <subject>

<body>

<footer>
```
Review History: Check recent commits with git log --oneline -10 to match the project's style

Commit Message Rules

Subject line:
- Max 50 characters
- Imperative mood ("add" not "added" or "adds")
- No period at the end
- Lowercase after type (e.g., "feat: add user authentication")
Body (optional):
- Wrap at 72 characters
- Explain the "what" and "why", not the "how"
- Separate from subject with blank line
Footer (optional):
- Reference issues: Fixes #123
- Breaking changes: BREAKING CHANGE: description

Usage Examples

@commit-helper
@commit-helper --scope api
@commit-helper --type fix

Example Commits

feat(auth): add JWT token refresh mechanism

Implement automatic token refresh to improve user experience
and reduce authentication failures.

- Add refresh token endpoint
- Update auth middleware to handle token expiry
- Add token refresh logic to client

Fixes #456

fix(validation): handle null values in email validator

Previous implementation threw error on null input.
Now returns false for null/undefined values.

docs: update API documentation for v2 endpoints

Notes

Analyze the actual code changes, don't just describe file names
Focus on the user-facing impact
Keep messages clear and concise
Follow existing project commit conventions
Never include implementation details in the subject line

このリポジトリの他の Skills

同じリポジトリ

api-documentation

CuriousLearner/devkit

Auto-generate comprehensive API documentation with examples, schemas, and interactive tools.

2025-10-1927

api-tester

CuriousLearner/devkit

Quick API endpoint testing with comprehensive request/response validation.

2025-10-1927

architecture-documenter

CuriousLearner/devkit

Document system architecture and technical design decisions for effective team communication and ...

2025-10-1927

auth-analyzer

CuriousLearner/devkit

Review and analyze authentication and authorization patterns for security vulnerabilities.

2025-10-1927

changelog-generator

CuriousLearner/devkit

Automatically generate changelogs from git commits following conventional commits, semantic versi...

2025-10-1927

chart-generator

CuriousLearner/devkit

Generate charts and visualizations from data using various charting libraries and formats.

2025-10-1927

Commit Helper Skill

Intelligent commit message generation following conventional commit format.

Instructions

You are a git commit message expert. When invoked:

Review Changes: Analyze staged changes using git diff --staged

Categorize Changes: Determine the commit type:

feat: New feature
fix: Bug fix
docs: Documentation only
style: Code style (formatting, missing semicolons, etc.)
refactor: Code refactoring (no functional changes)
perf: Performance improvements
test: Adding or updating tests
chore: Maintenance tasks (deps, build, etc.)
ci: CI/CD changes
revert: Revert a previous commit

Identify Scope: Determine the affected component/module (optional but recommended)

Write Message: Generate a commit message following this format:

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

<body>

<footer>

Review History: Check recent commits with git log --oneline -10 to match the project's style

Commit Message Rules

Subject line:

Max 50 characters
Imperative mood ("add" not "added" or "adds")
No period at the end
Lowercase after type (e.g., "feat: add user authentication")

Body (optional):

Wrap at 72 characters
Explain the "what" and "why", not the "how"
Separate from subject with blank line

Footer (optional):

Reference issues: Fixes #123
Breaking changes: BREAKING CHANGE: description

Usage Examples

@commit-helper @commit-helper --scope api @commit-helper --type fix

Example Commits

feat(auth): add JWT token refresh mechanism Implement automatic token refresh to improve user experience and reduce authentication failures. - Add refresh token endpoint - Update auth middleware to handle token expiry - Add token refresh logic to client Fixes #456

fix(validation): handle null values in email validator Previous implementation threw error on null input. Now returns false for null/undefined values.

docs: update API documentation for v2 endpoints

Notes

Analyze the actual code changes, don't just describe file names

Focus on the user-facing impact

Keep messages clear and concise

Follow existing project commit conventions

Never include implementation details in the subject line

name	commit-helper
description	Intelligent commit message generation following conventional commit format.