push

Commit and push Git changes while monitoring GitHub Actions deployments.

Updated May 14, 2026
One-click install
npx skills add https://github.com/bonjohen/claude-local --skill push-bonjohen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/bonjohen/claude-local/tree/main/bundle/skills/push
Command: npx skills add https://github.com/bonjohen/claude-local --skill push-bonjohen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pushes Git changes with confidence by automatically committing, pushing, monitoring the resulting GitHub Actions deployment, and iterating fixes when the build fails.

Core Features & Use Cases

  • Autonomous commit & push workflow: Detects staged/unstaged changes, creates a new commit with an optional provided message (or generates one), and pushes to the current branch without force-pushing.
  • Deployment monitoring with action-run correlation: Waits for the latest workflow run, polls status, and reports success with the deployment URL when available.
  • Autonomous CI failure repair loop: When the build fails, inspects failed logs, applies an appropriate code fix, commits it, and re-pushes up to three cycles to reach a successful deployment.

Quick Start

Run the push skill with an optional commit message to commit your pending changes, push them to origin, monitor the deployment, and automatically fix any CI build failures.

Frequently Asked Questions about push

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

FAQPage Schema
How do I automate git commits and push changes while monitoring GitHub Actions deployments?

Automated git commit and push workflows detect staged or unstaged changes, create commits with conventional messages, push to origin, and poll GitHub Actions runs to report deployment success or failure.

Can I automatically fix CI build failures after pushing code without manual intervention?

Yes, autonomous CI failure repair loops inspect failed GitHub Actions logs, apply appropriate code fixes, commit the changes, and re-push up to three cycles to achieve a successful deployment automatically.

What's the best way to self-heal failing GitHub Actions workflows from local edits?

Self-healing GitHub Actions workflows use a preflight gate to validate changes, execute a single-use push authorization, monitor the workflow run, and iterate on build failures by analyzing CI logs and applying automated fixes.

Does the automated push workflow support force-pushing to overwrite remote history?

No, the automated push workflow explicitly avoids force-pushing. It creates safe commits with conventional-message style and a co-author trailer, pushing changes to the current branch without overwriting remote repository history.

How do I ensure my staged and unstaged git changes are safely committed with conventional messages?

Safe commit creation detects pending staged and unstaged git changes, generates conventional-message style commit descriptions with a co-author trailer, and pushes to the current branch without requiring manual commit message formatting.

What happens when a GitHub Actions deployment fails during the automated push cycle?

When a GitHub Actions deployment fails, the workflow inspects failed CI logs, applies an appropriate code fix based on the error, commits the fix, and re-pushes up to three autonomous cycles until the deployment succeeds.