message-generation

Generate conventional commit messages following best practices

8 stars

Best use case

message-generation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Generate conventional commit messages following best practices

Teams using message-generation should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/message-generation/SKILL.md --create-dirs "https://raw.githubusercontent.com/dhofheinz/open-plugins/main/plugins/git-commit-assistant/commands/message-generation/skill.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/message-generation/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How message-generation Compares

Feature / Agent	message-generation	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Generate conventional commit messages following best practices

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Message Generation Skill - Semantic Commit Message Generation

Generate well-formatted commit messages that follow the Conventional Commits standard with proper type, scope, subject, body, and footer.

## Operations

- **subject** - Generate subject line: `<type>(<scope>): <description>`
- **body** - Compose commit body with bullet points
- **footer** - Add footer with breaking changes and issue references
- **validate** - Check conventional commits compliance
- **complete** - Generate full commit message (subject + body + footer)

## Router Logic

Parse $ARGUMENTS to determine which operation to perform:

1. Extract operation from first word of $ARGUMENTS
2. Extract remaining arguments as operation parameters
3. Route to appropriate instruction file:
   - "subject" → Read `/home/danie/projects/plugins/architect/open-plugins/plugins/git-commit-assistant/commands/message-generation/generate-subject.md`
   - "body" → Read `/home/danie/projects/plugins/architect/open-plugins/plugins/git-commit-assistant/commands/message-generation/write-body.md`
   - "footer" → Read `/home/danie/projects/plugins/architect/open-plugins/plugins/git-commit-assistant/commands/message-generation/add-footer.md`
   - "validate" → Read `/home/danie/projects/plugins/architect/open-plugins/plugins/git-commit-assistant/commands/message-generation/validate-message.md`
   - "complete" → Read `/home/danie/projects/plugins/architect/open-plugins/plugins/git-commit-assistant/commands/message-generation/complete-message.md`

4. Execute instructions with parameters
5. Return formatted commit message or validation results

## Error Handling

- If operation is unknown, list available operations
- If required parameters are missing, show required format
- If message validation fails, provide specific corrections
- If character limits exceeded, suggest rewording

## Usage Examples

```bash
# Generate subject line only
/message-generation subject type:feat scope:auth description:"add OAuth authentication"

# Write commit body
/message-generation body changes:"Implement OAuth2 flow,Add provider support,Include middleware"

# Add footer with issue references
/message-generation footer breaking:"authentication API changed" closes:123

# Validate existing message
/message-generation validate message:"feat(auth): add OAuth"

# Generate complete commit message
/message-generation complete type:feat scope:auth files:"src/auth/oauth.js,src/auth/providers.js"
```

## Conventional Commits Format

**Message Structure:**
```
<type>(<scope>): <subject>          ← Max 50 chars, imperative mood

<body>                               ← Optional, wrap at 72 chars
- Bullet point describing change 1
- Bullet point describing change 2

<footer>                             ← Optional
BREAKING CHANGE: description
Closes #123, #456
```

**Valid Types (priority order):**
1. feat - New feature
2. fix - Bug fix
3. docs - Documentation only
4. style - Formatting (no code change)
5. refactor - Code restructuring
6. perf - Performance improvement
7. test - Test additions/updates
8. build - Build system or dependencies
9. ci - CI/CD configuration
10. chore - Other maintenance
11. revert - Revert previous commit

---

**Base directory:** `/home/danie/projects/plugins/architect/open-plugins/plugins/git-commit-assistant/commands/message-generation`

**Current request:** $ARGUMENTS

Parse operation and route to appropriate instruction file.

Related Skills

specification-writing

from dhofheinz/open-plugins

Core reference for EARS requirement patterns, Given/When/Then acceptance criteria, RFC 2119 language, requirement ID conventions, and specification quality checklists. Background knowledge for the spec-writer agent. Preloaded by spec-writer via the skills frontmatter field; not user-invocable.

refine

from dhofheinz/open-plugins

Unified specification refinement plugin. Single entry point for all spec operations: greenfield architecture pipelines (principles → design → stack → spec → plan), feature spec creation in existing systems, iterative convergence loops, quality reviews, drift detection, finalization, ticket decomposition, traceable updates, and lifecycle archival. Detects pipeline state from existing artifact frontmatter and routes intelligently. Use whenever you need to create, refine, validate, or evolve a technical specification.

validation-orchestrator

from dhofheinz/open-plugins

Intelligent validation orchestrator with auto-detection and progressive validation workflows

security-scan

from dhofheinz/open-plugins

Comprehensive security scanning for secrets, vulnerabilities, and unsafe practices

schema-validation

from dhofheinz/open-plugins

Validate JSON schemas, required fields, and format compliance for marketplaces and plugins

quality-analysis

from dhofheinz/open-plugins

Deep quality analysis with scoring, recommendations, and actionable reports

documentation-validation

from dhofheinz/open-plugins

Validate documentation completeness, format, and quality for plugins and marketplaces

best-practices

from dhofheinz/open-plugins

Enforce OpenPlugins and Claude Code best practices for naming, versioning, and standards compliance

history-analysis

from dhofheinz/open-plugins

Analyze git history to learn project's commit style and conventions

commit-error-handling

from dhofheinz/open-plugins

Handle git errors and edge cases gracefully

commit-best-practices

from dhofheinz/open-plugins

Enforce git commit best practices and workflow guidance

commit-analysis

from dhofheinz/open-plugins

Analyze git changes to understand nature, scope, and commit type for intelligent message generation