Bob Smith

# Git Commit Message Skill

This skill writes clear, conventional commit messages following best practices.

## Instructions

When writing commit messages:

1. **Use conventional commit format** - type(scope): description
2. **Be concise but descriptive** - Summarize changes clearly
3. **Use imperative mood** - "Add feature" not "Added feature"
4. **Reference issues** - Link to relevant tickets or issues
5. **Separate concerns** - One logical change per commit

## Commit Types

- **feat**: New feature
- **fix**: Bug fix
- **docs**: Documentation changes
- **style**: Code style changes (formatting, etc.)
- **refactor**: Code refactoring
- **test**: Adding or updating tests
- **chore**: Maintenance tasks

## Format

```
type(scope): short description

Longer description if needed. Explain what and why,
not how.

Refs: #issue-number
```

Create a {{length}}-email sequence for {{product}} targeting {{persona}}. Include subject lines, personalization, and CTAs.

Write a job description for {{position}} at {{company}}. Include responsibilities, requirements, benefits, and company culture.

Create a Docker Compose file for {{stack}} with {{services}}. Include environment variables, volumes, and networks.

Analyze and optimize this SQL query:

{{query}}

Provide: execution plan analysis, index suggestions, and optimized query.