From session-closer
Provides the Conventional Commits format specification for git commit messages, including type definitions, formatting rules, and examples. Triggers on committing changes, writing commit messages, 'format my commit', 'how do I write a commit message', 'conventional commits', or 'what commit type should I use'. Also used by the session-closer-agent when committing session documentation.
npx claudepluginhub bartekck/bartek-marketplace --plugin session-closerThis skill uses the workspace's default tool permissions.
Format: `<type>(<optional scope>): <description>`
Generates Git commit messages following Conventional Commits spec with types like feat/fix/refactor, scopes, subject/body/footer guidelines, and issue references. Activates on commit requests or git mentions.
Formats Git commit messages according to Conventional Commits spec with types like feat/fix, scopes, bodies, and breaking changes. Enables automated changelogs and semantic versioning. Activates on commit writing or git mentions.
Guides Git commit messages to follow Conventional Commits v1.0.0 spec, covering types (feat, fix, refactor, etc.), scopes, structure, body, footers, and examples. Use for code commits and PR reviews.
Share bugs, ideas, or general feedback.
Format: <type>(<optional scope>): <description>
| Type | When to use |
|---|---|
feat | New feature or capability |
fix | Bug fix |
docs | Documentation only |
style | Formatting, whitespace — no logic change |
refactor | Code restructuring — no feature or fix |
perf | Performance improvement |
test | Adding or updating tests |
build | Build system or dependencies |
ci | CI/CD configuration |
chore | Maintenance tasks, tooling |
revert | Reverting a previous commit |
Historical note: Early commits in this project used a custom
sessiontype (e.g.,session(003): decisions from auth design). This is non-standard Conventional Commits. Usedocsfor session documentation commits.
type(scope): imperative description — max 72 charsfeat(auth):, fix(api):, session(003):)! after type/scope — feat!: remove legacy APIBREAKING CHANGE: description or Refs: #issuefeat(auth): add OAuth2 login flow
fix: resolve race condition in queue processor
docs(readme): update installation instructions
refactor(api): extract validation middleware
docs: add session 002 summary — plugin split and cleanup
feat(database): add connection pooling
Introduces configurable connection pool with min/max limits.
Defaults to 5 min, 20 max connections.
Refs: #142
BREAKING CHANGE: DATABASE_URL now requires pool parameters
When committing session documents:
docs — session files are project documentationdocs: add session 007 summary — auth system redesign