ada-git-pr-delivery

Converts uncommitted worktree changes into a verified pull request on a fresh branch.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/wubing7755/Ada --skill ada-git-pr-delivery-wubing7755
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ada-git-pr-delivery
Source: https://github.com/wubing7755/Ada/tree/main/skills/software-development/ada-git-pr-delivery
Command: npx skills add https://github.com/wubing7755/Ada --skill ada-git-pr-delivery-wubing7755

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Moving uncommitted work from a stale branch onto an updated main and opening a clean PR is error-prone: stale local main pointers block checkout, squash merges confuse history, tooling directories get committed accidentally, and PR checklists get ticked without actually running the gates. This Skill walks the full delivery path with verification at each step. ## Core Features & Use Cases - Stale-pointer recovery: Fixes a stale local main with git branch -f main origin/main from the current branch instead of losing work to stash or reset. - Clean staging and commit hygiene: Excludes tooling dirs and build artifacts via .gitignore checks, verifies staged content, and waits for explicit user approval before any commit. - PR base topology mapping: Uses merge-base and ..dev logs to pick the correct base branch instead of trusting a stale origin/HEAD. - Template-faithful PR creation: Fills the repo's pull_request_template.md sections, re-runs CI gates in order, creates the PR via gh, and verifies it is OPEN and MERGEABLE. - Use Case: You have a dirty worktree on an old feature branch and ask to pull latest main, carry all changes to a new branch, and open a PR — the Skill preserves every change, commits with a conventional message, and opens a verified PR. ## Quick Start Ask the agent to pull the latest main, carry all uncommitted changes onto a new feature branch, and open a pull request following the repo template.

Frequently Asked Questions about ada-git-pr-delivery

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

FAQPage Schema
How do I move uncommitted changes to a new branch and open a PR?

Fetch origin, fix the stale local main pointer with git branch -f main origin/main from your current branch, then checkout main and create the work branch — uncommitted changes carry over automatically. Verify the change count matches before and after, then commit and open the PR with gh.

Why does git checkout main fail with uncommitted changes?

The refusal usually means the local main pointer is stale and conflicts with the worktree, not a dirty-worktree policy. Fix the pointer from your current branch with git branch -f main origin/main, then checkout main; do not stash or reset first.

How do I choose the correct PR base branch when master and main both exist?

Do not trust refs/remotes/origin/HEAD, which may point at a stale branch. Map topology with git merge-base and git log --oneline <candidate-base>..dev, then pick the base whose log contains only the intended commits.

Can the agent commit my local changes without asking?

No. Local commits require explicit user review: the agent stages changes with git add and presents the change list, but waits for your approval before running git commit, even for unpushed local commits.

Why are source files missing after a fresh clone on Windows?

Windows gitignore matching is case-insensitive, so a lowercase pattern like src/Api/media/ can silently ignore a Media/ source directory. Verify with git ls-files --others and git check-ignore -v before committing new source directories.

When should I not use this PR delivery workflow?

Do not use it for destructive operations like resetting to origin or deleting local commits, history-preserving renames, deep PR code review, or batch phased delivery — those route to dedicated skills for each task.