ship-it

To enforce conventional commits and prevent direct pushes to main, this skill applies guardrails for branch management, requiring feature-branch sponsorship and PR-based integration. It formats PR titles and mandates branch cleanup after merges.

The best way to manage a git workflow for predictable code releases is to follow a disciplined process. This skill guides end-to-end changes from feature-branch creation through conventional commits, PR creation, and controlled release procedures.

To step through a feature-branch workflow for a pull request, initiate a feature change on a new branch, commit with a conventional message, open a PR with a properly formatted title, and run the post-merge release steps.

Yes, you can use this skill for Python package publishing on PyPI. It guides end-to-end release workflows from feature development to publishing, including optional PyPI release steps after your pull request is merged.

No, this skill prevents direct pushes to main for code integration. It requires pull-request based integration instead, enforcing conventional commit messages and formal release procedures to ensure predictable releases.

Conventional commit formatting improves code releases by ensuring changelog clarity and reviewability. This skill enforces conventional commits for every commit and PR title to maintain disciplined git workflows.