push

Commits pending changes, pushes to remote branch, and opens a PR with summary and test plan.

Updated May 23, 2026

Search Tags:#git #code review #pull request #commit #branch workflow #CI test plan

Ready to run

npx skills add https://github.com/devturco/thiago-dev-template --skill push-devturco

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: push
Source: https://github.com/devturco/thiago-dev-template/tree/main/.claude/skills/push
Command: npx skills add https://github.com/devturco/thiago-dev-template --skill push-devturco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents half-finished work by helping you reliably commit your current changes, push them to a safe branch, and open a pull request that explains what changed and why.

Core Features & Use Cases

Comprehensive change awareness: Reviews full git status and diff plus commit history on the branch (not just the latest commit) to inform the PR.
Conventional, safe commits: Guides a conventional-commit style message and explicitly avoids staging secrets or .env.
PR-ready workflow: Pushes to a remote branch with upstream tracking and creates a PR using gh with a structured, test-focused body.

Quick Start

Use the push skill to commit your current changes, push to your branch, and open a pull request with a detailed description and a specific test plan.

Frequently Asked Questions about push

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

FAQPage Schema

How do I commit, push, and open a pull request with a structured test plan?▼

To safely commit and push changes, stage your local git diff while explicitly excluding secrets and .env files, then push without force to a remote branch with upstream tracking before opening a PR.

How does a pull request generator analyze my branch changes?▼

A pull request generator analyzes branch changes by reviewing the full git status, complete diff, and entire commit history on the branch, rather than just the latest commit, to inform the PR description.

Can I use conventional commit messaging with Co-Authored-By attribution in my PR workflow?▼

Yes, you can use conventional commit messaging with Co-Authored-By attribution in your PR workflow to satisfy structured formatting requirements while pushing local changes and opening a collaborative pull request.

What is the best way to prevent staging secrets when pushing a commit to a remote branch?▼

The best way to prevent staging secrets when pushing a commit is to explicitly exclude .env files and secret files during the staging process, ensuring changes are pushed without force to a safe remote branch.

Does the PR creation process group change sections and enforce PR title and body length constraints?▼

Yes, the PR creation process enforces PR title and body length constraints, generates grouped change sections, and includes a concrete CI test plan by evaluating the full diff and commit range for collaborative review.

Why should I avoid force pushing when opening a pull request for code review?▼

You should avoid force pushing when opening a pull request because changes must be safely pushed to the correct remote branch with upstream tracking to preserve the commit history needed for collaborative code review.