commit

To create a git commit with sprint traceability, you stage changes and the skill reviews the diff, matches it to the active roadmap task, and proposes a conventional commits message with required trailers for approval.

Conventional commits compliance enforces a standardized commit message format that includes business-value and task references, ensuring backlog traceability by linking code changes directly to active sprint tasks.

Yes, you can run lint verification before committing because the skill performs pre-flight validation by reviewing staged files and executing lint checks, blocking the commit if project rules are violated.

No, this commit skill does not push code or create pull requests; it operates as a read-only, no-write, no-push approval flow, solely preparing and creating the local commit after you explicitly approve it.

The best way to link staged changes to a roadmap task is to let the skill inspect your diff and verify the active sprint task, which automatically builds the commit message with the required business-value references.

You should not use this automated conventional commits authoring tool when you have unstaged changes, as it requires staged diff review, or when your project lacks an active sprint task for traceability matching.