New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

PR Workflow

by Chorus-AIDLC in Chorus-AIDLC/Chorus

Complete workflow for submitting code changes — create branch, commit, open PR, check CI, fix failures, and merge.

AGPL-3.0Auto-check: notesDevelopment

Install PR Workflow

skills CLI
$ npx skills add Chorus-AIDLC/Chorus --skill pr-workflow -a claude-code

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

GitHub CLI
$ gh skill install Chorus-AIDLC/Chorus 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/Chorus-AIDLC/Chorus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/pr-workflow .claude/skills/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
pr-workflow
GitHub stars
1.2k
Token cost
~938 tokens
SKILL.md length
271 words
Files
1
Skills in repo
64
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Complete workflow for submitting code changes — create branch, commit, open PR, check CI, fix failures, and merge.

  • Works in 7 steps: Pre-flight Check → Create Branch → Stage and Commit → …
  • Tasks that involve Git workflow
  • SKILL.md covers Prerequisites, Steps and Checklist
  • Calls git, gh and npx; reaches claude.com

What it does

PR Workflow is an agent skill from Chorus-AIDLC/Chorus. Complete workflow for submitting code changes — create branch, commit, open PR, check CI, fix failures, and merge.

Its SKILL.md is about 940 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 Git workflow. The repository describes itself as: The Agent Harness for AI-Human Collaboration, inspired by the AI-DLC (AI-Driven Development Lifecycle). The licence is AGPL-3.0.

When your agent uses it

  • Tasks that involve Git workflow

Example prompts

  • “/pr-workflow”

Requirements

  • Node.js

Workflow steps

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

  1. Pre-flight Check
  2. Create Branch
  3. Stage and Commit
  4. Push and Open PR
  5. Check CI
  6. Fix CI Failures
  7. Merge

What it can do on your machine

Read from SKILL.md and the folder at commit 4754822. 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:

    • git
    • gh
    • npx
    • pnpm

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • claude.com

    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

PR Workflow loads about 938 tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 271 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
~938

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:33
    - No sensitive files (.env, credentials) staged

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 Chorus-AIDLC/Chorus at commit 4754822, republished under its AGPL-3.0 licence (© Chorus-AIDLC). 271 words, ~938 tokens.

Download SKILL.mdSave it as .claude/skills/pr-workflow/SKILL.md (or your agent's skills folder).
name
pr-workflow
description
Complete workflow for submitting code changes — create branch, commit, open PR, check CI, fix failures, and merge.
license
AGPL-3.0
metadata.author
chorus
metadata.version
0.1.0
metadata.category
development

PR Workflow

Complete workflow for taking local code changes through branch creation, PR, CI verification, failure fix, and merge.

Prerequisites

  • Code changes are already made and tested locally
  • Remote origin is configured
  • gh CLI is authenticated

Steps

1. Pre-flight Check
bash
git status
git diff --stat
git log --oneline -5

Verify before proceeding:

  • Only intended files are modified
  • No sensitive files (.env, credentials) staged
  • No temp artifacts (screenshots, logs) left behind
2. Create Branch

Branch from current HEAD. Naming convention:

TypePrefixExample
Bug fixfix/fix/remove-legacy-textarea
Featurefeat/feat/structured-ac-editor
Refactorrefactor/refactor/service-layer
Testtest/test/e2e-proposal-flow
Docsdocs/docs/api-reference
Chorechore/chore/bump-deps
bash
git checkout -b {prefix}{short-description}
3. Stage and Commit

Stage specific files only — never use git add . or git add -A:

bash
git add path/to/file1 path/to/file2

Note: Next.js paths need shell escaping:

bash
git add src/app/\(dashboard\)/projects/\[uuid\]/file.tsx

Commit with HEREDOC for clean multi-line messages:

bash
git commit -m "$(cat <<'EOF'
{type}: {concise description of why, not what}

{Optional body explaining context or trade-offs}

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
EOF
)"
4. Push and Open PR
bash
git push -u origin {branch-name}
bash
gh pr create --title "{type}: {title under 70 chars}" --body "$(cat <<'EOF'
## Summary
- Change 1
- Change 2

## Changed files
| File | Change |
|------|--------|
| `path/file.ts` | What changed |

## Test plan
- [x] Automated test passed
- [ ] Manual verification needed

Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
5. Check CI
bash
gh pr checks {pr-number}
  • All pass — report to user, ready for merge
  • Any fail — proceed to Step 6
6. Fix CI Failures

Get the failed logs:

bash
gh pr checks {pr-number}                          # find failed run ID
gh run view {run-id} --log-failed 2>&1 | tail -80  # read failure details

Common failure types and fixes:

FailureLocal reproFix
Test assertionnpx vitest run path/to/test.tsUpdate test expectations to match new behavior
Type errornpx tsc --noEmitFix types; check only your errors with | grep {keyword}
Lint errorpnpm lintAuto-fix or manual fix
Missing test updategrep -r "changedField" src/**/__tests__/Update test fixtures/helpers using the old field

After fixing:

bash
git add {fixed-files}
git commit -m "$(cat <<'EOF'
fix: {what was fixed in tests/types}

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
EOF
)"
git push

Re-check CI — repeat until green:

bash
gh pr checks {pr-number}
7. Merge

Only when user explicitly requests. Default to squash merge:

bash
gh pr merge {pr-number} --squash --delete-branch
git checkout main && git pull

Checklist

Before opening PR:

  • npx tsc --noEmit passes (or no new errors)
  • Related tests pass locally
  • No screenshots, temp files, or debug logs in working tree
  • Grep test files for any changed field/function names

Before merging:

  • CI is green
  • User has approved the merge

© Chorus-AIDLC, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/pr-workflow of Chorus-AIDLC/Chorus.

Open the folder on GitHubat commit 4754822

Compare with similar skills

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.

PR Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR Workflow this skillChorus-AIDLC/Chorus1.2k—~938Automated safety check: NotesAGPL-3.0
Kedro Babysitkedro-org/kedro11k—~4kAutomated safety check: PassCustom licence
Branch Regressionelodin-sys/elodin547—~1.6kAutomated safety check: PassApache-2.0
Fulfill Git Escrowinternet-court/internet-court-skill6.4k1 repos~1.2kAutomated safety check: NotesMIT
Git Upstream Syncwado-lang/wado117—~855Automated safety check: PassMIT
Qv SDK PR Statustetherto/qvac681—~638Automated safety check: PassApache-2.0

Similar skills

  • Kedro Babysit

    kedro-org/kedro

    Run Kedro's local lint / format / type-check / tests on changed files (uses the project's pre-commit hooks, ruff, mypy, pytest, lint-imports, detect-secrets, Make targets — in the right venv), or…

    11k GitHub stars~4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Branch Regression

    elodin-sys/elodin

    Compare two git branches (usually the current branch vs main) by running every example on each, capturing exit codes, logs, and editor screenshots, then diffing the results.

    547 GitHub stars~1.6k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Fulfill Git Escrow

    internet-court/internet-court-skill

    Fulfill a git escrow bounty by writing a solution or submitting an existing one.

    6.4k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check: notes

  • Git Upstream Sync

    wado-lang/wado

    The only way to merge origin/main into a branch, conflicts or not.

    117 GitHub stars~855 tokensUpdated today
    DevelopmentAuto-check passed

  • Qv SDK PR Status

    tetherto/qvac

    Team-wide PR dashboard for the SDK pod. An agent skill from tetherto/qvac.

    681 GitHub stars~638 tokensUpdated today
    DevelopmentAuto-check passed

  • PR Feedback Quality Gate

    nexu-io/open-design

    Safely track pull request feedback, resolve review comments or merge conflicts, validate fixes, and use a read-only cross-review before committing or pushing follow-up changes.

    100k GitHub stars~572 tokensUpdated today
    DevelopmentAuto-check passed

More from Chorus-AIDLC/Chorus

All 64 skills in this repo

  • E2E Verification

    Chorus-AIDLC/Chorus

    A skill your agent uses when manually verifying a Chorus frontend change in a real browser — finding local login credentials, driving the running dev server with the Playwright MCP, logging in…

    1.2k GitHub stars~1.5k tokensUpdated yesterday
    Auto-check: notes

  • Blog

    Chorus-AIDLC/Chorus

    Write release blog posts for Chorus — problem-first narrative, bilingual (zh/en), following the project's editorial style.

    1.2k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Brainstorm

    Chorus-AIDLC/Chorus

    Optional divergent-then-convergent dialogue for fuzzy ideas on Hermes.

    1.2k GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed

  • Brainstorm

    Chorus-AIDLC/Chorus

    Optional divergent-then-convergent dialogue for fuzzy ideas.

    1.2k GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed

  • Brainstorm Chorus

    Chorus-AIDLC/Chorus

    Optional divergent-then-convergent dialogue for fuzzy ideas.

    1.2k GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed

  • Chorus Brainstorm

    Chorus-AIDLC/Chorus

    Optional divergent-then-convergent dialogue for fuzzy ideas.

    1.2k GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about PR Workflow

What does PR Workflow do?

Complete workflow for submitting code changes — create branch, commit, open PR, check CI, fix failures, and merge. PR Workflow is an agent skill from Chorus-AIDLC/Chorus. Complete workflow for submitting code changes — create branch, commit, open PR, check CI, fix failures, and merge.

When should I use PR Workflow?

PR Workflow fits situations like: tasks that involve Git workflow.

How do I install PR Workflow in Claude Code?

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

How do I install PR Workflow in Codex?

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

Can I use 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 Chorus-AIDLC/Chorus --skill 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/pr-workflow, .gemini/skills/pr-workflow, .github/skills/pr-workflow and .opencode/skills/pr-workflow in your project.

What does PR Workflow need to run?

Going by SKILL.md and its folder, PR Workflow needs the command-line tools its instructions call (git, gh, npx and pnpm). Our summary lists: Node.js.

Does PR Workflow access the network?

SKILL.md names 1 domain. In commands or code: claude.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is PR Workflow safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does PR Workflow use?

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

How many tokens does PR Workflow use?

About 938 tokens (SKILL.md is roughly 3.8k 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 PR Workflow?

Skills that share tags, products or a category with PR Workflow: Kedro Babysit (kedro-org/kedro, 11k stars), Branch Regression (elodin-sys/elodin, 547 stars), Fulfill Git Escrow (internet-court/internet-court-skill, 6.4k stars) and Git Upstream Sync (wado-lang/wado, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Workflow?

Chorus-AIDLC (a GitHub organization) maintains it in Chorus-AIDLC/Chorus, which has 1,192 GitHub stars. The repository holds 64 skills in this directory. The repository was last updated on October 7, 2026.

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