Commit the staged changes to git with meaningful messages.
Generates git commit messages following project conventions and commits staged changes.
/plugin marketplace add Synthesys-Lab/agentize/plugin install agentize@agentizeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill instructs AI agent on how to commit staged changes to a git repository with meaningful commit messages.
The commit skill takes the following inputs:
issue-<number>-<brief-title>, so you can find the issue number from the branch name.The commit message should follow the structure below:
[tag]: A brief summary of the changes of this commit.
path/to/file/affected1: A brief description of changes made to this file.
path/to/file/affected2: A brief description of changes made to this file.
...
If needed, provide addtional context and explanations about the changes made in this commit.
It is preferred to mention the related Github issue if applicable.
A milestone commit is always on a development branch associated with a issue. If it is a milestone, additionally add the following information:
[milestone] before the tag.A milestone to issue #42.35/42 test cases passed.
The commit message should follow the structure below:
[tag]: A brief summary of the changes of this commit.
A short message is always for a delivery commit.
A git-msg-tags.md file should appear in {ROOT_PROJ}/docs/git-msg-tag.md which
defines the tags related to the corresponding modules or modifications. The AI agent
MUST refer to this file to select the appropriate tag for the commit message.
If not, reject the commit, and ask user to provide a list of tags in docs/git-msg-tag.md,
by showing the example format below:
Please provide a docs/git-msg-tags.md, which can be as simple as the following example:
# Git Commit Message Tags
- `[core]`: Changeing the core functionality of the project.
- `[docs]`: Changing the documentation.
- `[tests]`: Changes test cases.
- Use it only when solely changing the test cases! Do not mix with other changes with tests!
- `[build]`: Changes related to build scripts or configurations.
DO NOT claim the co-authorship of the commit with the user in the message. It is the user who is FULLY responsible for the commit.
When committing the changes, this skill should faithfully follow
the input on if it is a milestone to use --no-verify or not.
If it is a milestone, the commit MAY bypass pre-commit hooks.
If it is a delivery commit, the commit MUST NOT bypass pre-commit hooks!
DO NOT use pre-existing issue as an excuse to bypass pre-commit in any case!
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.