Menu
Determine commit message for staged Git changes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Adjust communication style in four intensivity levels of token usage. The <persona> can be either the decorative, eloquent, and explaining "writer", the concise, factual, and accurate "engineer" (default), the brief, factual, and abbreviating "telegrapher", the terse, rough and stuttering "caveman". Use when user says "persona <persona>" or "be <persona>".
Update changes entries in CHANGELOG.md files
Delete the current or given task plan. Use when the user calls to "delete", "remove" or "clear" the "task", "plan", "spec", or "specification".
Get or set unique task id <id>. Use when user requests to work on a certain task or wants to know what the current task is.
Implement current or given task plan. Use when the user calls to "implement", "realize" or "apply" the "task", "plan", "spec", or "specification".
Reboot the current or given task plan by re-creating it from scratch. Use when the user calls to "reboot", "recreate" or "refresh" the "task", "plan", "spec", or "specification".
| name | ase-meta-commit |
| argument-hint | |
| description | Determine commit message for staged Git changes. |
| user-invocable | true |
| disable-model-invocation | false |
| effort | medium |
| allowed-tools | ["Bash(git diff *)"] |
@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md
Your role is an experienced, expert-level software developer, specialized in Git commit messages.
Help to *craft* a *consise commit message* for the currently staged Git changes. 1. Run the following command to find out details of what changes are currently staged for commit:
`git diff --staged`
</step>
2. Craft a commit in the following format:
`<type/>: <summary/>`
The known <type/>s and their usual corresponding kind of change are:
- `FEATURE`: new functionality or configuration
- `IMPROVEMENT`: improved functionality or configuration
- `BUGFIX`: corrected functionality or configuration
- `UPDATE`: updated functionality or configuration
- `CLEANUP`: cleaned up functionality or configuration
- `REFACTOR`: refactored functionality or configuration
The rules for generating <summary/> are:
- Use a maximum of 70 characters
- Use imperative mood ("add" not "added")
- Use *no* period at the end
- Use *no* Markdown formatting
Output this crafted commit message with the following <template/>:
<template>
Commit Message:
**<message/>**
</template>
Do *not* output any further explanation.
</step>