skills.rest
cmetech
cmetechCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

upstream-cherry-pick

Audit upstream forks and file GitHub issues for cherry-pick candidates.

Updated May 25, 2026
Search Tags:#automation#github#audit#backlog#cherry-pick#triage#upstream
One-click install
npx skills add https://github.com/cmetech/otto-cli --skill upstream-cherry-pick
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upstream-cherry-pick
Source: https://github.com/cmetech/otto-cli/tree/main/.claude/skills/upstream-cherry-pick
Command: npx skills add https://github.com/cmetech/otto-cli --skill upstream-cherry-pick

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

OTTO's upstream cherry-pick audit automates the identification and triage of changes across vendored upstreams, building a durable backlog of candidate commits to port.

Core Features & Use Cases

  • Audit multiple upstreams (pi-dev, gsd-pi) to surface fixes and features for porting.
  • Classify each commit by applicability and severity, fetch related PR/issue context, and assess conflict risk against the divergence ledger.
  • File GitHub issues with detailed implementation guidance and a summary triage report; optionally run in dry-run or background mode for governance.

Quick Start

Run the deterministic audit workflow from the repository root with the bundled script, e.g., node .claude/skills/upstream-cherry-pick/scripts/run-audit.mjs <upstream>.

Frequently Asked Questions about upstream-cherry-pick

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate upstream cherry-pick triage for vendored forks?▼

Automating upstream cherry-pick triage involves scanning configured upstreams to classify commit applicability and severity, fetch PR context, and file GitHub issues. This skill runs that audit workflow deterministically to build a durable backlog of porting candidates.

What is upstream cherry-pick auditing and when do I need it?▼

Upstream cherry-pick auditing is the process of identifying and classifying changes across vendored upstreams to surface fixes and features for porting. You need it when maintaining forks and struggling to track which upstream commits should be backported.

Can I run a dry-run cherry-pick audit before filing GitHub issues?▼

Yes, you can run a dry-run cherry-pick audit to review candidate commits before any GitHub issues are filed. The audit supports dry-run mode and background execution to ensure safe governance and state management during the triage process.

Does the cherry-pick audit assess conflict risk against a divergence ledger?▼

Yes, the cherry-pick audit fetches related PR and issue context to score conflict risk against the divergence ledger. This assessment provides actionable implementation guidance directly within the filed GitHub issues and summary triage report.

How do I start an upstream audit using the bundled script?▼

To start an upstream audit, run the bundled script from the repository root using node .claude/skills/upstream-cherry-pick/scripts/run-audit.mjs <upstream>. This executes the deterministic audit workflow to scan and triage your configured upstreams.

Related Skills

Explore More Software Engineering Skills→
element22llcelement22llc
2

report

Report steer plugin defects via GitHub after deduplication and secrets scrubbing.

Official
Advanced
girijashankarjgirijashankarj
28

git-conflict-resolver

Classify and resolve git merge conflicts with guided validation steps.

Community
Advanced
glwrglwr
1

track

Audit project tracking health and align features/INDEX.md with GitHub Issues.

Community
Intermediate
spyqsspyqs

update-nanoclaw

Synchronize a customized NanoClaw fork with upstream updates via merge, cherry-pick, or rebase.

Community
Advanced