Commit with Agent Attribution
Create a semantic commit message that attributes the work to the agent.
Commit Message Format
{agent}: {type}: {description}
Components:
- agent: Name of the agent that did the work
- type: Type of change (feat, fix, chore, docs, refactor, test)
- description: Concise description of the change
Examples
planner: feat: generate implementation plan for user auth
implementor: feat: add OAuth authentication with Google provider
committer: chore: update dependencies to latest versions
Standard Agent Names
| Agent | Purpose |
|---|---|
planner |
Generated implementation plan |
implementor |
Implemented the solution |
classifier |
Classified the issue type |
reviewer |
Reviewed the changes |
Commit Types
| Type | Description |
|---|---|
feat |
New feature |
fix |
Bug fix |
chore |
Maintenance task |
docs |
Documentation changes |
refactor |
Code restructuring |
test |
Test additions or fixes |
Input Variables
- $1: Agent name (planner, implementor, etc.)
- $ARGUMENTS: Context for commit message
Rules
- Keep description under 72 characters
- Use present tense ("add" not "added")
- Don't end with a period
- Be specific about what changed
Generation Process
- Identify the agent from $1
- Determine the commit type from context
- Generate a concise description
- Format as:
{agent}: {type}: {description}
Context
Agent: $1 Changes: $ARGUMENTS
Converted and distributed by TomeVault — claim your Tome and manage your conversions.