git-push-and-tag

Automating git commit, push, and GitHub issue labeling requires a tool that stages changes, pushes to a remote repository, and applies a 'Ready' label to the associated issue. This skill handles all three operations in sequence using the gh CLI for issue interaction.

The best way to commit and push Git changes while updating a GitHub issue is using an automated workflow skill. It commits staged changes with an inferred message, pushes the branch, and signals readiness by labeling the corresponding GitHub issue.

Yes, you need the gh CLI to push Git changes and tag a GitHub issue. The skill requires the GitHub CLI for applying issue labels and the bd CLI for bead synchronization during the final phase of development workflows.

Automated Git push and tagging operates on issue branches following a specific naming convention. It is designed for the final phase of development workflows, ensuring code is versioned and issues are updated on branches that match this required format.

When automating Git push, the commit message is inferred by the skill. It stages changes and commits them automatically without requiring manual input, streamlining the process before pushing and tagging the GitHub issue.

Git workflow automation requires the bd CLI for bead synchronization to maintain project consistency. The tool uses it alongside the gh CLI to ensure local development states are synchronized before finalizing commits and tagging GitHub issues.