Agent skill

GitHub PR Workflow

by taracodlabs in taracodlabs/aiden

Pull request lifecycle: create, review, merge, manage (gh CLI)

Apache-2.0Auto-check passedDevelopment

Install GitHub PR Workflow

skills CLI
$ npx skills add taracodlabs/aiden --skill github-pr-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install taracodlabs/aiden github-pr-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/taracodlabs/aiden.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/github-pr-workflow .claude/skills/github-pr-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
github-pr-workflow
GitHub stars
849
Token cost
~887 tokens
SKILL.md length
259 words
Files
2
Skills in repo
63
Repo updated
First seen
Licence
Apache-2.0

At a glance

Pull request lifecycle: create, review, merge, manage (gh CLI)

  • Works in 9 steps: Create a pull request → List open PRs → View PR details and diff → …
  • Tasks that involve Pull requests
  • SKILL.md covers When to Use, How to Use, Examples and Cautions
  • Calls gh and git

What it does

GitHub PR Workflow is an agent skill from taracodlabs/aiden. Pull request lifecycle: create, review, merge, manage (gh CLI)

Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill.json`).

It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: Aiden — an autonomous AI agent and work engine built solo. It can operate your browser, terminal, files, apps, APIs, skills and tools, remember context, recover from failures… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/github-pr-workflow”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Create a pull request
  2. List open PRs
  3. View PR details and diff
  4. Check PR status and CI checks
  5. Review a PR (approve / request changes / comment)
  6. Merge a PR
  7. Checkout a PR locally
  8. Edit a PR (title, body, labels, reviewers)
  9. Close a PR without merging

What it can do on your machine

Read from SKILL.md and the folder at commit 3704204. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GitHub PR Workflow loads about 887 tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 259 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~20
When it runs · the whole SKILL.md, loaded when a task matches
~887

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from taracodlabs/aiden at commit 3704204, republished under its Apache-2.0 licence (© taracodlabs). 259 words, ~887 tokens.

Download SKILL.mdSave it as .claude/skills/github-pr-workflow/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
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
powershell
# 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
powershell
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
powershell
# 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
powershell
gh pr checks 15
gh pr status   # shows PRs relevant to you (authored, assigned, review requested)
5. Review a PR (approve / request changes / comment)
powershell
# 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
powershell
# 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
powershell
# 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)
powershell
# 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
powershell
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-branch removes 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 merge requires merge permissions — the user needs write access to the repo

© taracodlabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/github-pr-workflow of taracodlabs/aiden.

  • SKILL.md
  • skill.json

Open the folder on GitHubat commit 3704204

Compare with similar skills

GitHub PR Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

GitHub PR Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub PR Workflow this skilltaracodlabs/aiden849—~887Automated safety check: PassApache-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

More from taracodlabs/aiden

All 63 skills in this repo
  • Google Flights Search

    taracodlabs/aiden

    Searches Google Flights for prices, schedules and availability through browser automation with URL-based queries, and stops short of booking.

    849 GitHub stars~1.5k tokensUpdated 24 days ago
    Auto-check passed
  • OpenAI Codex CLI Bridge

    taracodlabs/aiden

    Delegates code generation, editing and explanation tasks to the OpenAI Codex CLI, with commands for interactive, auto-edit, question-only and model-specific runs.

    849 GitHub starsUsed in 1 repo~826 tokens
    Auto-check passed
  • Google Hotels Search

    taracodlabs/aiden

    Searches Google Hotels through the agent-browser tool for prices, ratings, amenities and availability, building a search URL from the location and dates and reporting a results table.

    849 GitHub stars~1.5k tokensUpdated 24 days ago
    Auto-check passed
  • Generates dark-themed architecture, component, data-flow and network diagrams as self-contained HTML and SVG files that open in any browser.

    849 GitHub stars~1.3k tokensUpdated 24 days ago
    Auto-check passed
  • Aggregates holdings across Zerodha, Upstox and Angel One and normalizes order parameters into one format, with confirmation required before any routing.

    849 GitHub stars~1.1k tokensUpdated 24 days ago
    Auto-check passed
  • arXiv Paper Search

    taracodlabs/aiden

    Searches arXiv by keyword, category, author or paper ID through its public API and downloads PDFs, with no API key needed.

    849 GitHub stars~1k tokensUpdated 24 days ago
    Auto-check passed

Works with

Categories

Questions about GitHub PR Workflow

What does GitHub PR Workflow do?

Pull request lifecycle: create, review, merge, manage (gh CLI). GitHub PR Workflow is an agent skill from taracodlabs/aiden.

When should I use GitHub PR Workflow?

GitHub PR Workflow fits situations like: tasks that involve Pull requests.

How do I install GitHub PR Workflow in Claude Code?

Run `npx skills add taracodlabs/aiden --skill github-pr-workflow -a claude-code`. Or copy the skill folder (skills/github-pr-workflow in taracodlabs/aiden) into .claude/skills/github-pr-workflow in your project. Claude Code loads it when a task matches its description.

How do I install GitHub PR Workflow in Codex?

Run `npx skills add taracodlabs/aiden --skill github-pr-workflow -a codex`. Or copy the skill folder (skills/github-pr-workflow in taracodlabs/aiden) into .agents/skills/github-pr-workflow in your project. Codex loads it when a task matches its description.

Can I use GitHub PR Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add taracodlabs/aiden --skill github-pr-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-pr-workflow, .gemini/skills/github-pr-workflow, .github/skills/github-pr-workflow and .opencode/skills/github-pr-workflow in your project.

What does GitHub PR Workflow need to run?

Going by SKILL.md and its folder, GitHub PR Workflow needs the command-line tools its instructions call (gh and git).

Does GitHub PR Workflow access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is GitHub PR Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does GitHub PR Workflow use?

GitHub PR Workflow is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitHub PR Workflow use?

About 887 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to GitHub PR Workflow?

Skills that share tags, products or a category with GitHub PR Workflow: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub PR Workflow?

taracodlabs (a GitHub organization) maintains it in taracodlabs/aiden, which has 849 GitHub stars. The repository holds 63 skills in this directory. The repository was last updated on September 13, 2026.

Source: taracodlabs/aiden on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.