push

Create branches and PRs, monitor CI, and merge after fixes.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/marcelocantos/skills --skill push-marcelocantos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/marcelocantos/skills/tree/main/skills/push
Command: npx skills add https://github.com/marcelocantos/skills --skill push-marcelocantos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the complex process of pushing code changes through pull requests and CI pipelines, reducing manual Git operations and ensuring smooth integration without errors.

Core Features & Use Cases

  • Branch and PR Management: Automatically creates feature branches and PRs from unpushed commits, with intelligent naming based on commit messages.
  • CI Monitoring and Fixes: Watches CI checks, diagnoses failures, applies fixes iteratively, and enforces project gates before merging.
  • Post-Merge Handling: Syncs local state after squash-merge and flushes pending documentation changes into a new PR.
  • Use Case: When working on a feature in a Git repo, use this Skill to branch, push, run CI, fix any issues, and merge once approved, streamlining team collaboration.

Quick Start

Invoke the push skill to handle creating a branch and PR for your current unpushed commits and monitor CI until ready to merge.

Frequently Asked Questions about push

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

FAQPage Schema
How do I automate Git pushes through PRs and CI workflows?

Automate Git pushes through PRs and CI workflows by invoking the push skill to create feature branches, generate PRs from unpushed commits, and monitor CI checks until ready to merge.

Can I automatically create a branch and PR from unpushed commits?

You can automatically create a branch and PR from unpushed commits using the push skill, which intelligently names branches and PRs based on commit messages.

How do I monitor CI checks and fix failures before merging a PR?

Monitor CI checks and fix failures before merging a PR by using the push skill to watch CI pipelines, diagnose failures iteratively, and enforce project gates prior to merge.

What is the best way to sync local Git state after a squash-merge?

The best way to sync local Git state after a squash-merge is using the push skill, which handles post-merge synchronization and flushes pending documentation changes into a new PR.

Do I need any external dependencies to automate code integration and testing?

You do not need any external dependencies to automate code integration and testing, as the push skill operates independently within Git repositories in software development scenarios.

When should I not use automated PR-based CI workflows for code delivery?

You should not use automated PR-based CI workflows for code delivery if your project lacks CI pipelines or requires manual Git operations without branch, PR, and gate enforcement integration.