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

Credited Community PR Harvest

by codewhale-hq in codewhale-hq/Codewhale

Lands exactly one approved community pull request onto the real release branch with its original authorship preserved, verified green, and posts a thank-you to the contributor.

MITAuto-check passedDevelopment

Install Credited Community PR Harvest

skills CLI
$ npx skills add codewhale-hq/Codewhale --skill gh-credit-harvest -a claude-code

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

GitHub CLI
$ gh skill install codewhale-hq/Codewhale gh-credit-harvest --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/codewhale-hq/Codewhale.git skills-src && mkdir -p .claude/skills && cp -r skills-src/docs/skills/gh-credit-harvest .claude/skills/gh-credit-harvest && 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
gh-credit-harvest
GitHub stars
41k
Token cost
~1.1k tokens
SKILL.md length
451 words
Files
1
Skills in repo
63
Repo updated
First seen
Licence
MIT

At a glance

Lands exactly one approved community pull request onto the real release branch with its original authorship preserved, verified green, and posts a thank-you to the contributor.

  • Works in 7 steps: Find the real landing branch (the one… → Review from evidence, not the title.… → Test mergeability against the REAL… → …
  • Landing one maintainer-approved community PR into the release branch
  • SKILL.md covers When to use, Workflow and Red flags / don't
  • Calls git, gh and cargo

What it does

This skill judges a pull request from its code, tests, comments and checks, never its title, and lands it only once a maintainer has already approved landing that specific PR into a release branch that may be local-only; it never merges, closes, tags or publishes on its own, leaving the PR closed by a separate workflow. It starts by switching to the real landing branch named by the maintainer, fetching the PR's head commit and reading its author to preserve, then reviewing the diff, tests, linked issue, comments and CI through the GitHub CLI rather than trusting the title.

Mergeability is tested against the real landing branch rather than the title's main-based flag, which can claim clean even when the release branch conflicts. Cherry-pick is the preferred landing method because it preserves the original author automatically; when a conflict, noise, or the need to squash makes that impractical, the change is re-applied as a narrow slice and committed with an explicit --author and a co-author trailer resolved from the project's AUTHOR_MAP, falling back to a numeric noreply address looked up through the GitHub API.

A specific commit-body line naming the harvested PR and its author is what a separate workflow file matches to auto-close the issue with credit once the commit reaches main. The final step formats the code and runs only the focused tests for the touched crate, landing only once that is green.

When your agent uses it

  • Landing one maintainer-approved community PR into the release branch
  • Preserving a contributor's authorship when cherry-picking their change
  • Re-applying a conflicting PR as a clean slice with correct credit trailers
  • Checking real mergeability against the release branch before harvesting a PR

Example prompts

  • “Harvest PR #512 into the release branch, preserving the contributor's authorship.”
  • “This PR conflicts with main but not the release branch. Cherry-pick it in and verify green.”
  • “Squash this contributor's commits but keep their name and credit trailer in the commit body.”
  • “Check this PR's real mergeability against the release branch before we land it.”

Requirements

  • The GitHub CLI (gh)
  • A local checkout with push access to the release branch
  • The project's AUTHOR_MAP for resolving co-author trailers

Workflow steps

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

  1. Find the real landing branch (the one the maintainer named, not always main) and fetch the PR head
  2. Review from evidence, not the title. Read the diff, tests, linked issue, comments, and CI
  3. Test mergeability against the REAL landing branch (local-only branches lie via the main flag)
  4. Land it, preferring cherry-pick — it preserves the original author automatically
  5. If it conflicts, spans noise, or needs squashing, re-apply the narrow slice and commit with explicit author + credit trailers. Resolve…
  6. Format and run the focused tests for the touched crate — only land green
  7. Post a brief, warm, specific thank-you on the PR — name what the change fixed, no drama. Leave the PR open; the workflow closes it with…

What it can do on your machine

Read from SKILL.md and the folder at commit 0ea319a. 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
    • cargo

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

  • Network

    No URLs in SKILL.md. Its commands use git and gh, 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

Credited Community PR Harvest loads about 1.1k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 451 words of instructions outside code blocks.

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

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 codewhale-hq/Codewhale at commit 0ea319a, republished under its MIT licence (© codewhale-hq). 451 words, ~1,119 tokens.

Download SKILL.mdSave it as .claude/skills/gh-credit-harvest/SKILL.md (or your agent's skills folder).
name
gh-credit-harvest
description
Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.

gh-credit-harvest

Harvest exactly one community PR into the real landing branch with full authorship and machine-readable credit, verified green, then thank the contributor. A PR is evidence: judge it from code, tests, comments, and checks, never the title. Do not merge, close, tag, or publish without maintainer approval — this skill lands a credited commit and posts thanks; the workflow closes the PR.

When to use

  • You have approval to land ONE specific community PR into a release branch.
  • The PR is not yet on the landing branch (if it is, close-with-credit instead — see gh-close-issues).
  • The landing branch may be local-only (e.g. <release-branch>); a main-based "mergeable" flag does not prove it lands cleanly.

Workflow

  1. Find the real landing branch (the one the maintainer named, not always main) and fetch the PR head:
    bash
    git switch <release-branch>
git fetch origin pull/<N>/head
git log -1 --format='%H %an <%ae>' FETCH_HEAD   # author to preserve
  2. Review from evidence, not the title. Read the diff, tests, linked issue, comments, and CI:
    bash
    gh pr view <N> --repo codewhale-hq/CodeWhale --json title,author,files,statusCheckRollup
gh pr diff <N> --repo codewhale-hq/CodeWhale
  3. Test mergeability against the REAL landing branch (local-only branches lie via the main flag):
    bash
    git merge-tree $(git merge-base HEAD FETCH_HEAD) HEAD FETCH_HEAD   # empty/clean = no conflict
  4. Land it, preferring cherry-pick — it preserves the original author automatically:
    bash
    git cherry-pick <sha>            # one or more commits from FETCH_HEAD
  5. If it conflicts, spans noise, or needs squashing, re-apply the narrow slice and commit with explicit author + credit trailers. Resolve --author and the co-author from .github/AUTHOR_MAP (fall back to numeric noreply):
    bash
    gh api users/<handle> --jq '"\(.id)+\(.login)@users.noreply.github.com"'
git commit --author="Name <ID+handle@users.noreply.github.com>" -m "fix(scope): what changed (#<N>)" \
  -m "Harvested from PR #<N> by @<handle>" \
  -m "Co-authored-by: Name <ID+handle@users.noreply.github.com>"
    The Harvested from PR #<N> by @<handle> line in the body is what .github/workflows/auto-close-harvested.yml matches to auto-close with credit once the commit reaches main.
  6. Format and run the focused tests for the touched crate — only land green:
    bash
    cargo fmt --all
cargo test -p <crate>            # the crate(s) the PR touched, not the whole workspace
git log -1 --format='%an <%ae>%n%(trailers:key=Co-authored-by)'  # credit the human, from .github/AUTHOR_MAP
  7. Post a brief, warm, specific thank-you on the PR — name what the change fixed, no drama. Leave the PR open; the workflow closes it with credit when the commit lands on main:
    bash
    gh pr comment <N> --repo codewhale-hq/CodeWhale \
  --body "Thank you @<handle> — clean fix for <the specific bug>. Harvested into the <release-branch> lane with your authorship preserved; it'll auto-close with credit once it reaches main."
Show full SKILL.md (174 more words)Show less

Shape of a clean harvest: a single-commit PR that cherry-picks with no conflicts needs no manual trailers — the author is preserved automatically — and a focused cargo test -p on the touched crate is enough to land it green.

Red flags / don't

  • Don't judge or land from the title or labels alone — read code, tests, comments, and checks.
  • Don't trust the GitHub main-based mergeable flag for a local-only release branch; prove it with git merge-tree.
  • Don't squash away the original author. Cherry-pick when you can; only fall back to --author + trailers when you must.
  • Don't invent co-author emails. Use .github/AUTHOR_MAP, then numeric noreply; never raw third-party, .local, placeholder, or bot emails.
  • Don't omit the Harvested from PR #<N> by @<handle> body line — without it the PR won't auto-close with credit.
  • Don't land red, harvest more than one PR per commit, or batch unrelated changes into the harvest.
  • Don't merge, close, tag, publish, or push release artifacts without maintainer approval. Keep the comment positive and crediting.
  • Already on the landing branch? Don't re-harvest — close-with-credit via gh-close-issues.

© codewhale-hq, MIT. 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 docs/skills/gh-credit-harvest of codewhale-hq/Codewhale.

Open the folder on GitHubat commit 0ea319a

Compare with similar skills

Credited Community PR Harvest 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.

Credited Community PR Harvest compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Credited Community PR Harvest this skillcodewhale-hq/Codewhale41k—~1.1kAutomated 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
Create Pull Request with Work Item IDmakeplane/plane61k—~824Automated safety check: PassAGPL-3.0
Creating Description For Gh PRredis/jedis12k—~838Automated safety check: PassMIT
Pascal Editor PR Openerpascalorg/editor25k—~619Automated safety check: PassMIT

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

  • 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 2 days ago
    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 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

  • 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

More from codewhale-hq/Codewhale

All 63 skills in this repo

  • Codewhale Dogfood Install

    codewhale-hq/Codewhale

    Proves a Codewhale change in the real product: a stamped release build, an atomic local install, fresh-shell verification and manual QA that automated gates cannot cover.

    41k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Codewhale Session Handoff

    codewhale-hq/Codewhale

    Writes a paste-ready handoff for the next agent session, opening with a state-check command block and separating done, suspected and blocked work.

    41k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Codewhale Landing Workflow

    codewhale-hq/Codewhale

    Decides how verified work should reach main, directly, in a worktree or on an integration branch, while keeping contributor credit and respecting merge gates.

    41k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Sub-Agent Delegation

    codewhale-hq/Codewhale

    Guides when and how to split multi-step coding, research or verification work into focused sub-agent runs while the parent keeps integration and final checks.

    41k GitHub stars~790 tokensUpdated today
    Auto-check passed

  • Codewhale Fleet Manager

    codewhale-hq/Codewhale

    Triages and manages Codewhale fleet runs and workers with typed commands, classifying failures and choosing a safe restart, resume or escalation.

    41k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • GitHub Issue Bulk Assigner

    codewhale-hq/Codewhale

    Moves a list of GitHub issues into a milestone or assigns them to owners with the gh CLI, checking each one before and after the change.

    41k GitHub stars~953 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Credited Community PR Harvest

What does Credited Community PR Harvest do?

Lands exactly one approved community pull request onto the real release branch with its original authorship preserved, verified green, and posts a thank-you to the contributor. This skill judges a pull request from its code, tests, comments and checks, never its title, and lands it only once a maintainer has already approved landing that specific PR into a release branch that may be local-only; it never merges, closes, tags or publishes on its own, leaving the PR closed by a separate workflow. It starts by switching to the real landing branch named by the maintainer, fetching the PR's head commit and reading its author to preserve, then reviewing the diff, tests, linked issue, comments and CI through the GitHub CLI rather than trusting the title.

When should I use Credited Community PR Harvest?

Credited Community PR Harvest fits situations like: landing one maintainer-approved community PR into the release branch; preserving a contributor's authorship when cherry-picking their change; re-applying a conflicting PR as a clean slice with correct credit trailers; checking real mergeability against the release branch before harvesting a PR.

How do I install Credited Community PR Harvest in Claude Code?

Run `npx skills add codewhale-hq/Codewhale --skill gh-credit-harvest -a claude-code`. Or copy the skill folder (docs/skills/gh-credit-harvest in codewhale-hq/Codewhale) into .claude/skills/gh-credit-harvest in your project. Claude Code loads it when a task matches its description.

How do I install Credited Community PR Harvest in Codex?

Run `npx skills add codewhale-hq/Codewhale --skill gh-credit-harvest -a codex`. Or copy the skill folder (docs/skills/gh-credit-harvest in codewhale-hq/Codewhale) into .agents/skills/gh-credit-harvest in your project. Codex loads it when a task matches its description.

Can I use Credited Community PR Harvest 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 codewhale-hq/Codewhale --skill gh-credit-harvest -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gh-credit-harvest, .gemini/skills/gh-credit-harvest, .github/skills/gh-credit-harvest and .opencode/skills/gh-credit-harvest in your project.

What does Credited Community PR Harvest need to run?

Going by SKILL.md and its folder, Credited Community PR Harvest needs the command-line tools its instructions call (git, gh and cargo). Our summary lists: The GitHub CLI (gh); A local checkout with push access to the release branch; The project's AUTHOR_MAP for resolving co-author trailers.

Does Credited Community PR Harvest access the network?

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

Is Credited Community PR Harvest 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 Credited Community PR Harvest use?

Credited Community PR Harvest 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 Credited Community PR Harvest use?

About 1.1k tokens (SKILL.md is roughly 4.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 Credited Community PR Harvest?

Skills that share tags, products or a category with Credited Community PR Harvest: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Create Pull Request with Work Item ID (makeplane/plane, 61k stars) and Creating Description For Gh PR (redis/jedis, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Credited Community PR Harvest?

codewhale-hq (a GitHub organization) maintains it in codewhale-hq/Codewhale, which has 41,082 GitHub stars. The repository holds 63 skills in this directory. The repository was last updated on October 11, 2026.

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