commit-pr

Commits, pushes, and opens draft GitHub pull requests with conventional commits and validation.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ZaxbyHub/ragappv3 --skill commit-pr-zaxbyhub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-pr
Source: https://github.com/ZaxbyHub/ragappv3/tree/main/.opencode/skills/commit-pr
Command: npx skills add https://github.com/ZaxbyHub/ragappv3 --skill commit-pr-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It standardizes how changes in the ragappv3 repository get committed, validated, pushed, and published as GitHub pull requests, preventing messy histories, unscoped staging, and unvalidated code from reaching review. ## Core Features & Use Cases - Branch Hygiene: Creates prefixed feature branches from master, handles detached HEAD states, and checks mergeability before pushing. - Scoped Validation: Runs targeted pytest and py_compile for backend Python changes, plus npm test, typecheck, lint, and build for frontend changes. - Review Follow-Up Handling: Classifies external review findings as confirmed, partially valid, not reproduced, pre-existing, or out of scope before applying fixes. - Use Case: After finishing a FastAPI bug fix, ask the agent to ship it; it stages only the touched files, runs the relevant tests, creates a conventional commit, pushes the branch, and opens a draft PR against master with a summary and test plan. ## Quick Start Commit my current changes and open a draft pull request against master with a proper test plan.

Frequently Asked Questions about commit-pr

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

FAQPage Schema
How do I create a draft pull request on GitHub from the command line?▼

Use the GitHub CLI with gh pr create --draft after pushing your branch with git push -u origin <branch>. This skill defaults to draft PRs against master unless you explicitly request a ready-for-review state.

How do I write conventional commit messages for a repository?▼

Use the format <type>(<scope>): <lowercase description> with types like feat, fix, test, docs, refactor, or chore. This skill keeps each PR branch to one meaningful conventional commit before requesting merge.

How should I handle external review findings on an existing pull request?▼

Verify each finding against the current diff and source before acting, then classify it as confirmed, partially valid, not reproduced, pre-existing, or out of scope. Fix confirmed findings, rerun focused validation, and summarize accepted, rejected, and deferred items in the PR body.

Can I safely force push after amending a commit on a PR branch?▼

Yes, use git push --force-with-lease -u origin <branch> after amending a review follow-up commit. Plain --force is never used because force-with-lease protects against overwriting others' changes on the remote.

What validation runs before publishing a frontend pull request?▼

Run npm run typecheck and npm run lint -- --max-warnings 0 from the frontend directory, plus targeted npm test for touched files. Run npm run build when changes affect build configuration, routing, or app shell behavior.