commit-push

Automate git commits, local validation, pushes, and draft PR management via GitHub CLI.

1|Updated May 12, 2018
One-click install
npx skills add https://github.com/tbroadley/dotfiles --skill commit-push-tbroadley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-push
Source: https://github.com/tbroadley/dotfiles/tree/main/claude/skills/commit-push
Command: npx skills add https://github.com/tbroadley/dotfiles --skill commit-push-tbroadley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual git workflows for commits, validations, pushing, PR creation and review can be error-prone and time-consuming.

Core Features & Use Cases

  • Pre-commit cleanup and local validation
  • Automated PR creation/update and drafting for feature branches
  • CI monitoring and reviewer communications to ensure green checks

Quick Start

To start, run the commit-push workflow on your current branch to commit changes, validate locally, push to origin, and open a draft PR.

Frequently Asked Questions about commit-push

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git commits, pushes, and pull request creation end-to-end?

You can automate the end-to-end git workflow by running a process that handles pre-commit cleanup, local validation checks, pushing to remote branches, and opening draft PRs. This replaces manual git workflow steps with a single automated sequence.

Can I automatically monitor CI checks and communicate with reviewers on a feature branch?

Yes, automated CI monitoring tracks check statuses during feature-branch development. The workflow monitors CI runs and handles reviewer communications to ensure your pull request receives green checks before merging.

Do I need the GitHub CLI to manage automated pull requests and draft updates?

Yes, GitHub CLI and GitHub API calls are required to manage PRs, checks, and communications. The automation relies on these tools to create pull requests, update drafts, and monitor CI status during feature-branch development.

What's the best way to handle pre-commit cleanup and local validation before pushing to a remote branch?

The best way is to use an automated workflow that performs pre-commit cleanup and runs local validation checks before pushing to origin. This ensures your feature branch passes local checks before remote submission and draft PR creation.

Why does manual git workflow for commits and PR review cause errors?

Manual git workflows for commits, validations, pushing, and pull request creation are error-prone and time-consuming because they require repeating multiple sequential steps by hand. Automating this workflow eliminates manual mistakes and reduces development time.

When should I not use an automated git workflow for commits and pull requests?

You should not use automated git workflows when your feature branch requires manual intervention for complex merge conflicts or custom commit message formatting. The automation covers standard pre-commit cleanup, validation, pushing, and draft PR management.