github-pr-workflow
Pull request lifecycle: create, review, merge, manage (gh CLI)
Install / Use
npx skills add taracodlabs/aiden --skill github-pr-workflowInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of github-pr-workflow
github-pr-workflow scores 85/100 on our quality scale, 1984th of 2,769 Automation skills we index.
Its SKILL.md is 3.5 KB long, well organised into 31 sections with 9 code examples: a solid amount of guidance for an agent.
It has 843 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so github-pr-workflow is actively maintained.
- Our last check on 2026-11-05 found the source still online.
- It is released under AGPL-3.0, a copyleft license: you can use it, but modified versions you distribute must carry the same license.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-06. Automated pattern scan on 2026-10-06. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
github-pr-workflow compared with similar skills
All 4 of these similar skills score higher than github-pr-workflow; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| github-pr-workflow (this skill)by taracodlabs | 85 | 843 | 2mo ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.7k | 9d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 82.0k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.9k | 8d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.9k | today | MCP Server |
Frequently asked questions
- How do I install github-pr-workflow?
- Run
npx skills add taracodlabs/aiden --skill github-pr-workflow. The install tabs above show the steps for each supported agent. - Which AI agents does github-pr-workflow work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is github-pr-workflow safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is AGPL-3.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is github-pr-workflow still maintained?
- The repository was last updated about 2 months ago, so github-pr-workflow is actively maintained.
Skill content
View source on GitHubname: github-pr-workflow description: "Pull request lifecycle: create, review, merge, manage (gh CLI)" category: developer version: 1.0.0 origin: aiden license: Apache-2.0 tags: github, pull-request, pr, review, merge, gh-cli, code-review, workflow, branch, diff
GitHub Pull Request Workflow
Manage the full lifecycle of GitHub pull requests — create, review, approve, request changes, merge, and clean up — using the gh CLI.
When to Use
- User wants to create a pull request from the current branch
- User wants to review or approve a PR
- User wants to merge a PR after approval
- User wants to check PR status, checks, or reviews
- User wants to list open PRs or find a specific PR
How to Use
1. Create a pull request
# Interactive (opens editor for body)
gh pr create
# Non-interactive with all fields
gh pr create --title "feat: add user authentication" --body "## Summary
- Add JWT-based auth
- Add login/logout endpoints
- Add middleware for protected routes
## Test plan
- [ ] Login with valid credentials
- [ ] Reject invalid credentials
- [ ] Access protected route with token" --base main --draft
2. List open PRs
gh pr list
gh pr list --state all --limit 20
gh pr list --author "@me"
gh pr list --label "ready for review"
3. View PR details and diff
# View PR summary
gh pr view 15
# View with comments
gh pr view 15 --comments
# Show diff
gh pr diff 15
4. Check PR status and CI checks
gh pr checks 15
gh pr status # shows PRs relevant to you (authored, assigned, review requested)
5. Review a PR (approve / request changes / comment)
# Approve
gh pr review 15 --approve --body "LGTM! Clean implementation."
# Request changes
gh pr review 15 --request-changes --body "Please add unit tests for the auth middleware."
# Leave a general comment
gh pr review 15 --comment --body "Looks mostly good — just one question inline."
6. Merge a PR
# Squash merge (recommended for feature branches)
gh pr merge 15 --squash --delete-branch
# Merge commit (preserves all commits)
gh pr merge 15 --merge
# Rebase merge
gh pr merge 15 --rebase --delete-branch
7. Checkout a PR locally
# Checkout a PR branch for local testing
gh pr checkout 15
# Return to main when done
git checkout main
8. Edit a PR (title, body, labels, reviewers)
# Mark draft as ready for review
gh pr ready 15
# Add reviewer
gh pr edit 15 --add-reviewer alice,bob
# Add label
gh pr edit 15 --add-label "ready for review"
9. Close a PR without merging
gh pr close 15 --comment "Closing in favour of PR #16 which takes a different approach."
Examples
"Create a PR from my current branch to main" → Use step 1 — fill in title and body describing the changes and test plan.
"Show me what CI checks are failing on PR 15"
→ Use step 4: gh pr checks 15 to see check names, status, and links to logs.
"Approve PR 22 and merge it with squash"
→ Use step 5 to approve, then step 6 with --squash --delete-branch.
Cautions
- Always check CI status (
gh pr checks) before merging — do not merge PRs with failing required checks --delete-branchremoves the remote branch after merge — confirm this is desired- Squash merge rewrites history — use merge commit for PRs where individual commit history matters
- Merging from
gh pr mergerequires merge permissions — the user needs write access to the repo
Related Skills
Agent-Reach
112.7kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
82.0k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.9kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.9k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
