git-pr

Automates commit, push, PR creation, and squash-merge across multiple git repositories.

3|1|Updated Nov 19, 2025
One-click install
npx skills add https://github.com/lukaskellerstein/claude-my-marketplace --skill git-pr-lukaskellerstein
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-pr
Source: https://github.com/lukaskellerstein/claude-my-marketplace/tree/main/plugins/dev-tools-plugin/skills/git-pr
Command: npx skills add https://github.com/lukaskellerstein/claude-my-marketplace --skill git-pr-lukaskellerstein

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Shipping feature-branch work across many git repositories requires repetitive manual steps — committing, pushing, opening PRs, merging, and returning to the default branch — which is slow and error-prone when done repo by repo. ## Core Features & Use Cases - Multi-repo batch shipping: Discovers every git repo in a folder and runs commit → push → PR → squash-merge → checkout main → pull for each one autonomously. - Safety guardrails: Refuses to commit secret-looking files (.env, keys, credentials), oversized files, or diverged branches, and never force-pushes, rebases, or uses admin merges. - Smart branch handling: Detects already-merged PRs, creates new feature branches for uncommitted work on the default branch, and enables GitHub auto-merge when checks block merging. - Use Case: After a day of edits across five microservice repos, run the skill once to ship every change as its own PR, merge them, and leave all repos clean on main. ## Quick Start Ask the assistant to commit and ship all repos in the current folder as PRs and get everything back to the main branch.

Frequently Asked Questions about git-pr

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

FAQPage Schema
How do I create and merge PRs across multiple git repos at once?▼

Run the git-pr skill in a folder containing multiple repositories. It discovers each repo, commits pending work, pushes the branch, opens or reuses a PR, squash-merges it, then checks out and pulls the default branch for every repo.

How do I commit changes on main without pushing directly to the default branch?▼

The skill detects uncommitted work on the default branch and automatically creates a new feature branch for it. The changes are committed there, pushed, and merged through a PR instead of touching the default branch directly.

Does this workflow work with the GitHub CLI?▼

Yes, the GitHub CLI (gh) is required for PR creation and merging. The script verifies gh is installed and authenticated before shipping, and stops with a clear message if it cannot see the repository on GitHub.

What happens if a repo contains a file that looks like a secret?▼

The script stops for that repo before committing and reports which file looks like a secret, such as .env, key files, or credentials JSON. Other repos in the batch still complete normally, and the flagged file is never opened or committed.

Can it force-push or bypass branch protection rules?▼

No. The script never force-pushes, rebases, amends, or uses admin merges. If checks or reviews block a merge, it enables GitHub auto-merge so the PR merges only after requirements pass.