TypingMindTypingMindThe best frontend for AI
Github Pr Workflow logo

Github Pr Workflow

Organization
taracodlabs
github-pr-workflow

Full pull request lifecycle — create, review, merge, and manage PRs using the gh CLI

Overview

Publishertaracodlabs
Repositoryaiden
Skill namegithub-pr-workflow
Stars
865
Forks
149
Bundled files
1
LicenseApache-2.0
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by taracodlabs on GitHub. Read the source before you install it.

Installation

Install the Github Pr Workflow AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/taracodlabs/aiden/tree/main/workspace-templates/skills/github-pr-workflow
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/taracodlabs/aiden.git /tmp/aiden
mkdir -p .claude/skills
cp -r /tmp/aiden/workspace-templates/skills/github-pr-workflow .claude/skills/github-pr-workflow
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Github Pr Workflow in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Github Pr Workflow on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Github Pr Workflow is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Github Pr Workflow AI skill do?

Full pull request lifecycle — create, review, merge, and manage PRs using the gh CLI

Why use Github Pr Workflow on TypingMind?

Because you install it once and use it with any model. Github Pr Workflow is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Github Pr Workflow in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/taracodlabs/aiden/tree/main/workspace-templates/skills/github-pr-workflow. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Github Pr Workflow?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Github Pr Workflow?

As many as you like. As long as a model supports skills, you can use Github Pr Workflow with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Github Pr Workflow AI skill free?

Yes. It is published on GitHub by taracodlabs under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
openclaw logo

Openclaw Pr Maintainer

openclaw
OrganizationPopular

Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.

82.2K
391K
5 files
View
openclaw logo

Openclaw Refactor Docs

openclaw
OrganizationPopular

Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.

82.2K
391K
Instructions
View
openclaw logo

Openclaw Repair Sweep

openclaw
OrganizationPopular

Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

82.2K
391K
1 files
View
openclaw logo

Openclaw Test Performance

openclaw
OrganizationPopular

Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.

82.2K
391K
1 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇