commit

Committing and pushing changes to Git involves staging your modifications, creating a commit with a descriptive message, and pushing to the remote repository. This Skill automates that workflow by reviewing your branch strategy, inspecting the diff, composing a commit message, and executing the push after your approval.

Branch-scoped commits follow a naming convention with appropriate prefixes and contain clear, focused changes. This Skill applies your project's branch strategy to suggest the right prefix, validate your changes against the current status, and ensure commits are structured for user review before pushing.

Use git status to see modified files and git diff to inspect the exact changes line by line. This Skill displays both, lets you review the recommended commit message, and requires your approval before executing the commit and push to your remote branch.

Yes. This Skill lists available branches and lets you choose the appropriate target—whether creating a new feature branch or pushing to an existing one. It respects your branch strategy and applies the correct prefix for the branch type you select.

This Skill presents a recommended commit message and awaits your approval before executing. You can review and refine the message during this step, ensuring it accurately describes your changes before the commit and push are applied to the remote.

Yes. This Skill reads your project's branch strategy to determine naming conventions and prefixes, then applies those standards when suggesting branch names and composing commit messages, ensuring your changes follow the established workflow.