Agent skill

GitHub PR Workflow

by HybridAIOne in HybridAIOne/hybridclaw

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

MITAuto-check passedDevelopment

Install GitHub PR Workflow

skills CLI

$ npx skills add HybridAIOne/hybridclaw --skill github-pr-workflow -a claude-code

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

GitHub CLI

$ gh skill install HybridAIOne/hybridclaw 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/HybridAIOne/hybridclaw.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/

Paste into Claude Code

Install the "github-pr-workflow" agent skill from https://github.com/HybridAIOne/hybridclaw/tree/main/skills/github-pr-workflow into .claude/skills/github-pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-pr-workflow", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/HybridAIOne/hybridclaw/tree/main/skills/github-pr-workflow

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add HybridAIOne/hybridclaw --skill github-pr-workflow -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install HybridAIOne/hybridclaw github-pr-workflow --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/HybridAIOne/hybridclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/github-pr-workflow .agents/skills/github-pr-workflow && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "github-pr-workflow" agent skill from https://github.com/HybridAIOne/hybridclaw/tree/main/skills/github-pr-workflow into .agents/skills/github-pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-pr-workflow", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add HybridAIOne/hybridclaw --skill github-pr-workflow -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install HybridAIOne/hybridclaw github-pr-workflow --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/HybridAIOne/hybridclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/github-pr-workflow .cursor/skills/github-pr-workflow && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "github-pr-workflow" agent skill from https://github.com/HybridAIOne/hybridclaw/tree/main/skills/github-pr-workflow into .cursor/skills/github-pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-pr-workflow", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/HybridAIOne/hybridclaw.git --path skills/github-pr-workflow

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add HybridAIOne/hybridclaw --skill github-pr-workflow -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install HybridAIOne/hybridclaw github-pr-workflow --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/HybridAIOne/hybridclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/github-pr-workflow .gemini/skills/github-pr-workflow && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "github-pr-workflow" agent skill from https://github.com/HybridAIOne/hybridclaw/tree/main/skills/github-pr-workflow into .gemini/skills/github-pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-pr-workflow", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install HybridAIOne/hybridclaw github-pr-workflow

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add HybridAIOne/hybridclaw --skill github-pr-workflow -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/HybridAIOne/hybridclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/github-pr-workflow .github/skills/github-pr-workflow && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "github-pr-workflow" agent skill from https://github.com/HybridAIOne/hybridclaw/tree/main/skills/github-pr-workflow into .github/skills/github-pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-pr-workflow", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add HybridAIOne/hybridclaw --skill github-pr-workflow -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install HybridAIOne/hybridclaw github-pr-workflow --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/HybridAIOne/hybridclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/github-pr-workflow .opencode/skills/github-pr-workflow && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "github-pr-workflow" agent skill from https://github.com/HybridAIOne/hybridclaw/tree/main/skills/github-pr-workflow into .opencode/skills/github-pr-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-pr-workflow", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: github-pr-workflow
GitHub stars: 158
Token cost: ~929 tokens
SKILL.md length: 397 words
Files: 1
Skills in repo: 70
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

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

Works in 9 steps: Verify GitHub CLI authentication if the… → Sync the base branch. → Create a focused branch for one change. → …
Tasks that involve Pull requests
SKILL.md covers Default Sequence, Core Commands, CI and Merge Readiness and Review Feedback Loop, plus 2 more sections
Calls gh and git

What it does

GitHub PR Workflow is an agent skill from HybridAIOne/hybridclaw. Create branches, commit and push changes, open or update GitHub pull requests, handle CI, and merge safely.

Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests and Git workflow. It works with GitHub. The repository describes itself as: Enterprise-ready self-hosted AI assistant runtime with sandboxed execution, secure credentials, approvals, and memory. The licence is MIT.

When your agent uses it

Tasks that involve Pull requests
Tasks that involve Git workflow

Example prompts

“/github-pr-workflow”

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

Verify GitHub CLI authentication if the workflow will use gh.
Sync the base branch.
Create a focused branch for one change.
Implement and validate locally.
Commit with a clear message.
Push and open or update the PR.
Check CI and fix failures.
Address review feedback.
Merge only when the branch is green and approved.

What it can do on your machine

Read from SKILL.md and the folder at commit 48ac731. 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 929 tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 397 words of instructions outside code blocks.

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

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 HybridAIOne/hybridclaw at commit 48ac731, republished under its MIT licence (© HybridAIOne). 397 words, ~929 tokens.

Download SKILL.mdSave it as .claude/skills/github-pr-workflow/SKILL.md (or your agent's skills folder).

name: github-pr-workflow
description: Create branches, commit and push changes, open or update GitHub pull requests, handle CI, and merge safely.
user-invocable: true

GitHub PR Workflow

Use this skill for the end-to-end pull request loop from branch creation through merge readiness.

Default Sequence

Verify GitHub CLI authentication if the workflow will use gh.
Sync the base branch.
Create a focused branch for one change.
Implement and validate locally.
Commit with a clear message.
Push and open or update the PR.
Check CI and fix failures.
Address review feedback.
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" --body-file /tmp/pr-body.md
gh pr view --web

If gh is unavailable, complete the local git steps and use the GitHub UI for PR-specific actions.

CI and Merge Readiness

Check status after every push:

bash

gh pr checks
gh pr checks --watch
gh run list --branch "$(git branch --show-current)" --limit 5
gh run view <run-id> --log-failed

When a check fails:

inspect the failing job or logs
reproduce locally if possible
fix the smallest confirmed problem
rerun targeted validation
push again and re-check CI

Do not merge red CI unless the user explicitly accepts that risk.

Show full SKILL.md (146 more words)Show less

Review Feedback Loop

Use the PR conversation as the source of truth:

bash

gh pr view 123 --comments
gh pr comment 123 --body "Addressed the failing migration path."
gh pr review 123 --comment --body "Applied the requested cleanup."

When feedback arrives:

group related comments into one fix pass when practical
mention what changed, not just that it is done
rerun the checks most likely to regress
keep follow-up commits small and labeled by intent

Merge Options

Use the repository's preferred merge style:

bash

gh pr merge 123 --squash
gh pr merge 123 --merge
gh pr merge 123 --rebase

Before merging, verify:

CI is green
required reviewers approved
the PR description still matches the implementation
no unresolved review threads remain if the repo treats them as blockers

Working Rules

Prefer small PRs over broad mixed-scope branches.
Keep the PR body current when scope changes.
Do not hide risky follow-up work in "later" comments; put it in the PR body or linked issue.
If a change needs multiple dependent PRs, make the stack explicit.
When CI is noisy or flaky, call that out instead of pretending the branch is stable.

Files

Just SKILL.md in skills/github-pr-workflow of HybridAIOne/hybridclaw.

Open the folder on GitHubat commit 48ac731

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
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
GitHub PR Workflow this skillHybridAIOne/hybridclaw	158	—	~929	Automated safety check: Pass	MIT	today
Contributor-First PR MergeHKUDS/OpenHarness	16k	1 repos	~847	Automated safety check: Pass	MIT	4 mo ago
Create Pull Requestcline/cline	70k	1 repos	~1.6k	Automated safety check: Pass	Apache-2.0	today
Creating Description For Gh PRredis/jedis	12k	—	~838	Automated safety check: Pass	MIT	today
Create Pull Request with Work Item IDmakeplane/plane	61k	—	~824	Automated safety check: Pass	AGPL-3.0	today
React Router Pull Request Creatorremix-run/react-router	57k	—	~2.5k	Automated safety check: Pass	MIT	yesterday

Similar skills

Contributor-First PR Merge
HKUDS/OpenHarness
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
Create Pull Request
cline/cline
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
Creating Description For Gh PR
redis/jedis
Official
Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.
12k GitHub stars~838 tokensUpdated today
DevelopmentAuto-check passed
Create Pull Request with Work Item ID
makeplane/plane
Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.
61k GitHub stars~824 tokensUpdated today
DevelopmentAuto-check passed
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
57k GitHub stars~2.5k tokensUpdated yesterday
DevelopmentAuto-check passed
Pascal Editor PR Opener
pascalorg/editor
Opens or refreshes a pull request on pascalorg/editor from the current branch, describing only what the branch's commits and diff actually contain.
25k GitHub stars~619 tokensUpdated today
DevelopmentAuto-check passed

Questions about GitHub PR Workflow

What does GitHub PR Workflow do?

Create branches, commit and push changes, open or update GitHub pull requests, handle CI, and merge safely. GitHub PR Workflow is an agent skill from HybridAIOne/hybridclaw. Create branches, commit and push changes, open or update GitHub pull requests, handle CI, and merge safely.

When should I use GitHub PR Workflow?

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

How do I install GitHub PR Workflow in Claude Code?

Run `npx skills add HybridAIOne/hybridclaw --skill github-pr-workflow -a claude-code`. Or copy the skill folder (skills/github-pr-workflow in HybridAIOne/hybridclaw) 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 HybridAIOne/hybridclaw --skill github-pr-workflow -a codex`. Or copy the skill folder (skills/github-pr-workflow in HybridAIOne/hybridclaw) 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 HybridAIOne/hybridclaw --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 MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitHub PR Workflow use?

About 929 tokens (SKILL.md is roughly 3.7k 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: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Creating Description For Gh PR (redis/jedis, 12k stars) and Create Pull Request with Work Item ID (makeplane/plane, 61k 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?

HybridAIOne (a GitHub organization) maintains it in HybridAIOne/hybridclaw, which has 158 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 7, 2026.

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

Install GitHub PR Workflow

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

GitHub PR Workflow

Default Sequence

Core Commands

Verify GitHub CLI Auth

Prepare the Branch

Commit Clearly

Push and Open the PR

CI and Merge Readiness

Review Feedback Loop

Merge Options

Working Rules

Files

Compare with similar skills

Similar skills

More from HybridAIOne/hybridclaw

Related

Questions about GitHub PR Workflow