git-commit-push-pr

Commit, push, and open GitHub pull requests with adaptive value-first descriptions.

Updated May 11, 2026
One-click install
npx skills add https://github.com/mmnavarr/harness --skill git-commit-push-pr-mmnavarr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-push-pr
Source: https://github.com/mmnavarr/harness/tree/main/skills/git-commit-push-pr
Command: npx skills add https://github.com/mmnavarr/harness --skill git-commit-push-pr-mmnavarr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Going from working-tree changes to an open pull request involves many error-prone steps: branching off the default branch, staging the right files, following commit conventions, detecting existing PRs, and writing a description that matches the change's complexity. This Skill automates that entire workflow in one pass. ## Core Features & Use Cases - End-to-end PR workflow: Gathers git context, detects conventions from commit history, branches, commits, pushes, and creates the PR via the GitHub CLI. - Adaptive PR descriptions: Scales description depth to the change size, from one sentence for a typo fix to full narratives with Mermaid diagrams and comparison tables for architectural changes. - Description-only updates: Refreshes an existing PR's description against the full branch diff, with user confirmation before applying. - Use Case: You finish a bugfix on a feature branch and say "commit and PR" — the Skill commits with a conventional message, pushes, and opens a PR whose description explains the problem and fix without boilerplate. ## Quick Start Ask the assistant to commit my current changes, push them, and open a pull request with a description sized to the change.

Frequently Asked Questions about git-commit-push-pr

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

FAQPage Schema
How do I commit, push, and open a GitHub PR in one step?▼

Invoke the workflow with a phrase like "commit and PR" or "ship this". It gathers git status and diff, creates a feature branch if needed, commits following repo conventions, pushes with git push -u origin HEAD, and creates the PR using gh pr create.

How to update an existing pull request description on GitHub?▼

Ask to update or refresh the PR description. The Skill locates the open PR for the current branch with gh pr view, regenerates the description from the full branch diff against the base branch, summarizes the changes, and applies it with gh pr edit after your confirmation.

Does this work with fork-based pull requests and non-origin remotes?▼

Yes. Base branch detection uses a fallback chain: existing PR metadata, origin/HEAD symbolic ref, GitHub default branch via gh repo view, then common branch names. It matches the PR's base repository against local remotes so fork workflows using an upstream remote resolve correctly.

What happens if I run it on the main or master branch?▼

The Skill detects when the current branch is the default branch and asks whether to create a feature branch first, deriving a descriptive name from the change content. If you decline, it stops rather than pushing directly to the default branch.

How does it decide how long the PR description should be?▼

It sizes the change along two axes — number of files and diff size, plus complexity such as design decisions or trade-offs. Small simple changes get one or two sentences, while large architectural changes get full narratives with optional Mermaid diagrams and comparison tables.

What are the limitations of the PR detection logic?▼

Detection relies on gh pr view for the current branch and deliberately avoids gh pr list --head, which can match the wrong PR in multi-fork repos. Non-zero exits from auth, network, or repo configuration errors stop the workflow and are reported to the user.