원클릭으로 Manus에서 모든 스킬 실행

시작하기

commit-helper

스타15

포크5

업데이트2026년 3월 23일 07:13

Create well-structured conventional commit messages from staged changes

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

gastown-publish

gastown-publish/gasclaw

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Commit Helper

Analyze staged changes and create a well-structured conventional commit message.

Commit Format

<type>(<scope>): <summary>

<body>

<footer>

Type

Determine from the staged changes:

Type	Condition
`feat`	New files, new functions, new capabilities
`fix`	Bug fixes, error handling corrections
`perf`	Performance optimizations
`test`	Test files only (new or updated)
`docs`	Documentation/markdown only
`refactor`	Restructuring without behavior change
`build`	Build configs, Makefile, Dockerfile
`ci`	CI/CD files (.github/workflows, etc.)
`chore`	Dependency updates, config tweaks

Scope

Derive from changed files:

If all changes are in one directory: use that directory name
If changes span a module: use the module name
If changes are cross-cutting: omit scope or use a descriptive word

Summary Line

Imperative mood: "add" not "added" or "adds"
Lowercase first letter
No trailing period
Max 50 characters
Completes the sentence: "This commit will ___"

Body (optional but recommended for non-trivial changes)

Separated from summary by a blank line
Wrap at 72 characters
Explain what and why, not how (the diff shows how)
Use bullet points for multiple changes

Footer (optional)

Fixes #<issue> for bug fix PRs
Related to #<issue> for feature work
BREAKING CHANGE: <description> for breaking changes

Workflow

Step 1: Analyze Staged Changes

# See what's staged
git diff --cached --stat

# See the actual changes
git diff --cached

# See untracked files (might need staging)
git status --short

Step 2: Determine Commit Type and Scope

Read the staged diff and categorize:

What type of change is this? (feat, fix, refactor, etc.)
What area is affected? (directory, module, component)
What is the primary intent of the change?

Step 3: Write the Message

Compose the commit message following the format above.

Step 4: Create the Commit

git commit -m "<type>(<scope>): <summary>

<body>

<footer>"

Or if amending:

git commit --amend -m "<type>(<scope>): <summary>

<body>

<footer>"

Step 5: Verify

# Check the commit was created
git log --oneline -1

# Verify the full message
git log -1 --format="%B"

Examples

Simple feature:

feat(cli): add verbose flag to status command

Bug fix with body:

fix(proxy): handle connection timeout during key rotation

The key rotation loop was not catching ConnectionError exceptions,
causing the entire health monitor to crash when the upstream API
was temporarily unreachable.

Fixes #23

Multi-file refactor:

refactor(bootstrap): extract service startup into dedicated functions

- Move dolt startup to _start_dolt()
- Move daemon startup to _start_daemon()
- Move mayor startup to _start_mayor()

Each function now handles its own retry logic and error reporting,
making the bootstrap sequence easier to test and debug.

Test addition:

test(health): add edge cases for activity compliance check

Cover scenarios where:
- Agent has no commits at all
- Agent's last commit is exactly at the deadline
- Clock skew between agent and server

Rules

Never commit unstaged changes: Only describe what's in git diff --cached
One logical change per commit: If staged changes are unrelated, suggest splitting
No WIP commits on shared branches: If changes are incomplete, suggest a more descriptive message
Reference issues: Always link to issues when applicable
Check before committing: Verify tests pass with make test if available

이 저장소의 다른 Skills

같은 저장소

gasclaw-config

gastown-publish/gasclaw

View and edit gasclaw maintainer configuration at runtime

2026-04-2215

gastown-update

gastown-publish/gasclaw

Check and apply updates to all Gastown dependencies

2026-04-2215

create-pr

gastown-publish/gasclaw

Create a well-structured PR with conventional commit title and descriptive body

2026-03-2315

monitor-pr-ci

gastown-publish/gasclaw

Monitor PR CI checks and review comments, auto-fix failures and address feedback

2026-03-2315

pr-review

gastown-publish/gasclaw

Review a pull request for code quality, test coverage, security, and best practices

2026-03-2315

docstring

gastown-publish/gasclaw

Write docstrings for PyTorch functions and methods following PyTorch conventions. Use when writing or updating docstrings in PyTorch code.

2026-03-2315

name	commit-helper
description	Create well-structured conventional commit messages from staged changes
metadata	{"openclaw":{"emoji":"📝","os":["linux"],"requires":{"bins":["git"]}}}
parameters	{"amend":{"type":"string","description":"Amend the previous commit instead of creating new: true or false (default: false)","required":false}}

Commit Helper

Analyze staged changes and create a well-structured conventional commit message.

Commit Format

<type>(<scope>): <summary>

<body>

<footer>

Type

Determine from the staged changes:

Type	Condition
`feat`	New files, new functions, new capabilities
`fix`	Bug fixes, error handling corrections
`perf`	Performance optimizations
`test`	Test files only (new or updated)
`docs`	Documentation/markdown only
`refactor`	Restructuring without behavior change
`build`	Build configs, Makefile, Dockerfile
`ci`	CI/CD files (.github/workflows, etc.)
`chore`	Dependency updates, config tweaks

Scope

Derive from changed files:

If all changes are in one directory: use that directory name
If changes span a module: use the module name
If changes are cross-cutting: omit scope or use a descriptive word

Summary Line

Imperative mood: "add" not "added" or "adds"
Lowercase first letter
No trailing period
Max 50 characters
Completes the sentence: "This commit will ___"

Body (optional but recommended for non-trivial changes)

Separated from summary by a blank line
Wrap at 72 characters
Explain what and why, not how (the diff shows how)
Use bullet points for multiple changes

Footer (optional)

Fixes #<issue> for bug fix PRs
Related to #<issue> for feature work
BREAKING CHANGE: <description> for breaking changes

Workflow

Step 1: Analyze Staged Changes

# See what's staged
git diff --cached --stat

# See the actual changes
git diff --cached

# See untracked files (might need staging)
git status --short

Step 2: Determine Commit Type and Scope

Read the staged diff and categorize:

What type of change is this? (feat, fix, refactor, etc.)
What area is affected? (directory, module, component)
What is the primary intent of the change?

Step 3: Write the Message

Compose the commit message following the format above.

Step 4: Create the Commit

git commit -m "<type>(<scope>): <summary>

<body>

<footer>"

Or if amending:

git commit --amend -m "<type>(<scope>): <summary>

<body>

<footer>"

Step 5: Verify

# Check the commit was created
git log --oneline -1

# Verify the full message
git log -1 --format="%B"

Examples

Simple feature:

feat(cli): add verbose flag to status command

Bug fix with body:

fix(proxy): handle connection timeout during key rotation

The key rotation loop was not catching ConnectionError exceptions,
causing the entire health monitor to crash when the upstream API
was temporarily unreachable.

Fixes #23

Multi-file refactor:

refactor(bootstrap): extract service startup into dedicated functions

- Move dolt startup to _start_dolt()
- Move daemon startup to _start_daemon()
- Move mayor startup to _start_mayor()

Each function now handles its own retry logic and error reporting,
making the bootstrap sequence easier to test and debug.

Test addition:

test(health): add edge cases for activity compliance check

Cover scenarios where:
- Agent has no commits at all
- Agent's last commit is exactly at the deadline
- Clock skew between agent and server

Rules

Never commit unstaged changes: Only describe what's in git diff --cached
One logical change per commit: If staged changes are unrelated, suggest splitting
No WIP commits on shared branches: If changes are incomplete, suggest a more descriptive message
Reference issues: Always link to issues when applicable
Check before committing: Verify tests pass with make test if available