skills.rest
zhiyuan-zhang0206
zhiyuan-zhang0206COMMUNITY
Explore all skills by this author →
GitHub

pr

Validates commits, pushes, and pull request creation against repository hygiene and CI-readiness checklists.

1|Updated Aug 14, 2026
Search Tags:#git#code review#pull request#commit#github#gh cli#ci
One-click install
npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill pr-zhiyuan-zhang0206
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/zhiyuan-zhang0206/Ava/tree/main/ava_builtins/plugins/ava_code/skills/pr
Command: npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill pr-zhiyuan-zhang0206

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents broken pushes and phantom pull requests by enforcing a pre-push self-check, verifying that PRs are actually created, and keeping commit history clean before code reaches CI. ## Core Features & Use Cases - Pre-push self-check: Confirms the branch is rebased on the latest main, conflicts are resolved, commit messages follow convention with the Co-authored-by trailer, and local checks pass before pushing. - PR creation and verification: Creates pull requests with gh pr create and immediately verifies existence with gh pr list, so a returned GitHub URL is never mistaken for an actual PR. - Dependency declaration and repo hygiene: Declares dependencies on unmerged PRs in the description and keeps scratch files out of the repository by staging paths explicitly with git status. - Use Case: Before opening a PR that depends on an unmerged schema change, run the checklist, declare "> Depends on: #XXX" in the description, create the PR, and verify it appears in gh pr list. ## Quick Start Before I push this branch, run the PR self-check, create the pull request with gh, and verify it was actually created.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I create a pull request with the GitHub CLI?▼

Create a pull request with gh pr create --base main --title "..." --body "...", then verify it exists by running gh pr list --head with your current branch. The URL GitHub prints after a push is only a creation page, not an actual PR.

What should I check before pushing commits to GitHub?▼

Confirm the branch is rebased on the latest main, no conflict markers remain, the commit message follows convention including the Co-authored-by trailer, and all local checks for the touched scope pass. Push only when everything is green locally.

How do I declare a dependency on another unmerged PR?▼

Add a line at the top of the PR description such as "> Depends on: #XXX — can only rebase and pass CI once that is merged." This tells reviewers that CI failures stem from the missing dependency, not your changes.

Why does my pull request not exist after pushing?▼

Pushing only returns a link to a page for creating a PR; it does not create one. Run gh pr create explicitly, then check gh pr list --head with your branch — if it returns empty, the PR was never created.

How do I avoid committing scratch files to a repository?▼

Keep PR-body and commit-message drafts under /tmp/ instead of the repo, and confirm each path with git status before staging. Avoid git add -A or git add . so temporary files never enter permanent git history.

Related Skills

Explore More Software Engineering Skills→
TalonT-OrgTalonT-Org
5

resolve-failures

Apply targeted code fixes to failing test suites in a Git worktree.

Official
Advanced
dimakisdimakis

land-pr

Shepherd GitHub pull requests through CI checks, reviews, and squash merges.

Community
Intermediate
ql-linkql-link
5

doc-maintenance-sync

Update AGENTS.md and docs sections to reflect current codebase changes.

Official
Intermediate
heyzudeheyzude
4

yeet

Stage, commit, and open a GitHub pull request using Git and the GitHub CLI.

Community
Intermediate