github-pr-workflow

Solid

Create branches, commit and push changes, open or update GitHub pull requests, handle CI, and merge safely.

AI & Automation 125 stars 11 forks Updated today MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
70
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# GitHub PR Workflow Use this skill for the end-to-end pull request loop from branch creation through merge readiness. ## Default Sequence 0. Verify GitHub CLI authentication if the workflow will use `gh`. 1. Sync the base branch. 2. Create a focused branch for one change. 3. Implement and validate locally. 4. Commit with a clear message. 5. Push and open or update the PR. 6. Check CI and fix failures. 7. Address review feedback. 8. Merge only when the branch is green and approved. ## Core Commands ### Verify GitHub CLI Auth ```bash gh auth status ``` Run this before any git or PR workflow steps that depend on `gh`. If it fails, fix authentication first so the workflow does not stop later during `gh pr create`, `gh pr checks`, or other PR commands. ### Prepare the Branch ```bash git fetch origin git checkout main git pull --ff-only origin main git checkout -b feat/short-description ``` Use the repository's actual base branch if it is not `main`. ### Commit Clearly ```bash git status --short git add path/to/file.ts tests/path/to/file.test.ts git commit -m "feat: short summary" ``` Keep commits scoped and explain user-visible intent in the subject line. ### Push and Open the PR ```bash git push -u origin HEAD gh pr create --fill ``` When `--fill` is not enough, make the body explicit with: - summary - test plan - risks or rollout notes - linked issue or ticket Useful variants: ```bash gh pr create --draft gh pr create --base main --title "feat: short summary"...

Details

Author
HybridAIOne
Repository
HybridAIOne/hybridclaw
Created
5 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category