Pick PR's from git branch A to B. Create separated PR's on github. Don't put your name into this PR's and don't sign
commits. Don't need much description - just refer original PR.
For example: from release/3.4 to main
erigon-cherry-pick
Erigon cherry pick PR's from one long-living git branch to another
v1.0LATEST
NewUpdated Aug 20, 2026
Overall Score
38/100
Grade
D
Below Average
Grades are signals, not a certification. Always review a skill yourself before use.
Safety
72
Quality
25
Clarity
45
Completeness
22
Summary
This skill guides an AI agent to cherry-pick pull requests from one long-living git branch to another (e.g., from release/3.4 to main), create separate PRs on GitHub, and maintain clean commit attribution by avoiding personal names and signatures. The skill is intended for managing backports or forward-ports of changes across release branches.
Detected Capabilities
git operationsbash executionfile read/writegithub api interaction
Trigger Keywords
Phrases that agents use to match this skill to user intent.
cherry pick commitsbackport pr changessync release branchesforward port featuresgithub branch sync
Risk Signals
INFO
No security-relevant patterns detected in static pre-scan
full-content
INFO
Skill uses allowed-tools: Bash, Read, Write, Edit, Glob, Git — all declared and scoped
frontmatter
INFO
Git operations are project-scoped and destructive risk is minimal (cherry-pick is non-destructive)
intent
Use Cases
- Backport fixes from stable releases to main branch
- Forward-port features to upcoming release branches
- Sync changes across multiple long-living branches in Git repositories
- Automate cherry-pick PR workflows in Erigon project
Quality Notes
- Skill content is extremely sparse — only one sentence of instruction provided
- No step-by-step guidance on how to identify PRs to cherry-pick
- No error handling documented (merge conflicts, CI failures, PR rejection scenarios)
- Missing details on GitHub API integration or PR creation mechanism
- No edge cases addressed (PR already merged, conflicting changes, etc.)
- Constraint about 'don't put your name' and 'don't sign commits' is clear but incomplete — no guidance on how to achieve this in git configuration
- No documentation of expected inputs (which PRs, which branches) or outputs (links to created PRs)
- Scope is clear (cherry-pick between branches) but execution details are absent
Model: claude-haiku-4-5-20251001Analyzed: Aug 20, 2026
Reviews
Add this skill to your library to leave a review.
No reviews yet
Be the first to share your experience.
Use fauziyasin-s2m4qw/erigon-cherry-pick in your dev environment — a Developer account adds skills to your library and syncs them via the SkillRepo CLI.