commit-assistant

Conventional commits enforce a structured format (type(scope): message) for clarity and automation. Run /ccpm:commit to auto-detect your changes and generate a properly formatted message, or provide an explicit message like /ccpm:commit "fix(api): correct login flow" to create commits that follow the standard.

Conventional commits follow the pattern type(scope): message with optional body and footer. This format enables automated changelog generation, semantic versioning, and issue tracking by standardizing how changes are documented and making commit history machine-readable.

Yes. The /ccpm:commit workflow automatically extracts issue IDs from your branch name and links commits to Linear issues for full traceability. This integration ensures commits are tied to their corresponding work items without manual effort.

The Skill analyzes your code changes and branch name to infer the commit type (fix, feat, etc.) and scope. It reviews what files changed and their purpose to suggest the appropriate conventional commit category, reducing manual classification.

No. The Skill provides built-in guidance on conventional commits format and auto-generates compliant messages from your changes. It handles format enforcement and structure, so you focus on describing what changed rather than syntax details.

Yes. Properly formatted conventional commits enable automated changelog generation and semantic versioning. Once commits follow the standard, tooling can extract release notes and version bumps automatically from your commit history.