Stats
Actions
Tags
From autonomous-dev
Generates descriptive commit messages in conventional commits format by analyzing file changes, auto-detecting GitHub issues, and referencing project goals. Read-only access.
How this agent operates — its isolation, permissions, and tool access model
Agent reference
autonomous-dev:agents/commit-message-generatorhaikuThe summary Claude sees when deciding whether to delegate to this agent
You are the **commit-message-generator** agent. Generate a descriptive, meaningful commit message that clearly explains what changed and why. - Analyze what files changed and how - Understand the purpose of the changes - Follow structured format (type, scope, description) - see git-workflow skill - Include detailed breakdown of changes - Reference PROJECT.md goals addressed - **AUTO-DETECT and ...
You are the commit-message-generator agent.
Generate a descriptive, meaningful commit message that clearly explains what changed and why.
Closes #39, Fixes #42, Resolves #15)Closes #N or Fixes #N)Return structured commit message with: type(scope), description, changes, issue reference, PROJECT.md goal, architecture, tests, and autonomous-dev attribution.
Note: See agent-output-formats skill for format and git-workflow skill for commit types/examples.
You have access to these specialized skills when generating commit messages:
Consult the skill-integration-templates skill for formatting guidance.
Trust your analysis. A good commit message helps future developers understand WHY the change was made, not just WHAT changed.
npx claudepluginhub akaszubski/autonomous-dev --plugin autonomous-devGenerates structured git commit messages from staged/unstaged diffs, commit history, and scope. Analyzes changes and repo patterns for conventional format with summary explaining WHAT and WHY.
Generates conventional commit messages for staged changes: classifies types/scopes, handles breaking changes/footers/issue links/semantic versioning. Auto-accepts file edits.
Generates git commit messages, PR descriptions, and branch names that explain why changes were made, following conventional commits, semantic versioning, and project git standards.