rc-git

Creates branches, commits, pushes, and opens pull requests with confirmation gates and rebase conflict resolution.

19|1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/rodolfochicone/rc-project --skill rc-git-rodolfochicone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rc-git
Source: https://github.com/rodolfochicone/rc-project/tree/main/skills/promoted/rc-git
Command: npx skills add https://github.com/rodolfochicone/rc-project --skill rc-git-rodolfochicone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Moving local work to a reviewed pull request involves many error-prone git steps — branching off the default branch, writing good commit and PR messages, pushing safely, and handling rebases and merge conflicts. This Skill walks through each outward-facing step with explicit confirmation so nothing is pushed or published by accident. ## Core Features & Use Cases - Branch, Commit, Push, PR Workflow: Inspects real repository state, summarizes the actual diff, proposes conventional branch names, and opens a PR via the GitHub CLI with a pt-BR description template. - Confirmation Gates: Commit, push, and PR creation each require separate explicit approval, and the PR target branch is always confirmed rather than assumed. - Rebase & Conflict Resolution: Provides a strategy decision matrix (squash-first, interactive, rerere, merge-instead), conflict resolution patterns, troubleshooting guides, and helper scripts for backup, conflict analysis, and merge validation. - Use Case: You finished a feature on main with uncommitted changes. Invoke the skill to create feat/my-feature, commit the work, push it, and open a PR against the correct target branch — confirming each step along the way. ## Quick Start Ask the agent to ship the current local changes as a pull request, optionally providing a Linear issue ID for the branch name.

Frequently Asked Questions about rc-git

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

FAQPage Schema
How do I create a branch, commit, and open a GitHub pull request?▼

The skill inspects your repo state, summarizes the diff, proposes conventional branch names like feat/short-slug, then commits, pushes with git push -u, and opens the PR via gh pr create. Each outward-facing step requires your explicit confirmation before running.

How to resolve git rebase conflicts without losing work?▼

Create a timestamped backup branch first, then choose a strategy such as squash-first for 3+ commits so conflicts are resolved once. Resolve markers by understanding both sides, validate with lint and tests, and force-push only with --force-with-lease.

What happens if the gh CLI is not installed when opening a PR?▼

The skill does not fail silently. It prints the GitHub compare URL for your branch and target so you can open the pull request manually in the browser.

When should I merge instead of rebase a branch?▼

Use git merge instead of rebase on shared branches, critical production code without comprehensive tests, or when multiple people push to the same branch. When uncertain, merge is the safer default.

How do I recover lost commits after a force push?▼

Restore from the timestamped backup branch created before the rebase using git reset --hard backup-rebase-<timestamp>. Alternatively, find the commit SHA with git reflog and reset to it.