commit-and-push

To write clean commit messages and link issues, this skill automates commit grouping and formats messages using Conventional Commits. It links commits to specific issues only after receiving explicit user confirmation for the tracking linkage.

The best way to prepare a pull request with issue tracking is to automate PR preparation alongside issue-aware commits. This skill generates appropriate PR titles and handles issue closures based on explicit user input.

Conventional Commits formatting enforces code hygiene by structuring commit messages with clear scopes and types. This skill implements this standard during the commit grouping process to maintain a clean, readable project history.

You do not need to manually link commits to issues. This skill requires explicit user input to confirm issue linkage, ensuring commits are properly tracked and pushed without automatic assumptions about issue associations.

Yes, you can group code changes before creating a pull request. This skill handles scope determination and commit grouping to organize your changes logically before formatting the final commit messages and PR recommendations.

You should not use automated commit and push workflows when you need to push changes without explicit issue linkage. This skill requires user confirmation for issue tracking and PR creation, making it unsuitable for rapid untracked pushes.