Menu
Create well-structured conventional commit messages from staged changes
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
View and edit gasclaw maintainer configuration at runtime
Check and apply updates to all Gastown dependencies
Create a well-structured PR with conventional commit title and descriptive body
Monitor PR CI checks and review comments, auto-fix failures and address feedback
Review a pull request for code quality, test coverage, security, and best practices
Write docstrings for PyTorch functions and methods following PyTorch conventions. Use when writing or updating docstrings in PyTorch code.
| 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}} |
Analyze staged changes and create a well-structured conventional commit message.
<type>(<scope>): <summary>
<body>
<footer>
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 |
Derive from changed files:
Fixes #<issue> for bug fix PRsRelated to #<issue> for feature workBREAKING CHANGE: <description> for breaking 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
Read the staged diff and categorize:
Compose the commit message following the format above.
git commit -m "<type>(<scope>): <summary>
<body>
<footer>"
Or if amending:
git commit --amend -m "<type>(<scope>): <summary>
<body>
<footer>"
# Check the commit was created
git log --oneline -1
# Verify the full message
git log -1 --format="%B"
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
git diff --cachedmake test if available