Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.
68
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
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 Hunter's approval — this skill lands a credited commit and posts thanks; the workflow closes the PR.
gh-close-issues).<release-branch>); a main-based "mergeable" flag does not prove it lands cleanly.main) and fetch the PR head:
git switch <release-branch>
git fetch origin pull/<N>/head
git log -1 --format='%H %an <%ae>' FETCH_HEAD # author to preservegh pr view <N> --repo Hmbown/CodeWhale --json title,author,files,statusCheckRollup
gh pr diff <N> --repo Hmbown/CodeWhalegit merge-tree $(git merge-base HEAD FETCH_HEAD) HEAD FETCH_HEAD # empty/clean = no conflictgit cherry-pick <sha> # one or more commits from FETCH_HEAD--author and the co-author from .github/AUTHOR_MAP (fall back to numeric noreply):
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>"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.cargo fmt --all
cargo test -p <crate> # the crate(s) the PR touched, not the whole workspace
python3 scripts/check-coauthor-trailers.py --author-map .github/AUTHOR_MAP --range HEAD~1..HEAD --check-authorsmain:
gh pr comment <N> --repo Hmbown/CodeWhale \
--body "Thank you @<handle> — clean fix for <the specific bug>. Harvested into the v0.8.61 lane with your authorship preserved; it'll auto-close with credit once it reaches main."Grounded example: PR #3221 by @hongchen1993 (honour DEEPSEEK_BASE_URL/DEEPSEEK_MODEL in exec) cherry-picks cleanly, so its author is preserved with no manual trailers; a focused cargo test -p on the touched crate is enough to land it green.
git merge-tree.--author + trailers when you must..github/AUTHOR_MAP, then numeric noreply; never raw third-party, .local, placeholder, or bot emails.Harvested from PR #<N> by @<handle> body line — without it the PR won't auto-close with credit.gh-close-issues.f018d3e
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.