Coordinates upstream cherry-pick issue porting into otto-cli with lanes and gates.
npx skills add https://github.com/cmetech/otto-cli --skill upstream-fix-cmetech
Please help me install this Agent Skill. Skill: upstream-fix Source: https://github.com/cmetech/otto-cli/tree/main/.claude/skills/upstream-fix Command: npx skills add https://github.com/cmetech/otto-cli --skill upstream-fix-cmetech
Implement upstream-cherry-pick issues on cmetech/otto-cli. This skill coordinates planning, porting, testing, and review across file-disjoint git-worktree lanes to ensure safe, auditable upstream integrations.
Port selected upstream issues into otto-cli by running the upstream-fix workflow with the desired filters and gates.
High-intent search queries and answers about installing and using this skill.
The best way to port upstream cherry-pick fixes is using a deterministic workflow that groups issues into file-disjoint git-worktree lanes, ensuring safe parallel integration. This coordinates planning, selective porting, testing gates, and independent reviews into otto-cli.
Lane planning works by grouping upstream cherry-pick issues by target files to maximize parallelism while avoiding conflicts. It assigns issues to deterministic, file-disjoint git-worktree lanes so engineers can port fixes concurrently and safely into otto-cli.
You handle interrupted upstream porting runs by checking the maintained ledger of lanes and issues. This ledger tracks statuses, SHAs, guidance paths, and PRs to support resumable runs and provide full traceability for auditing upstream integrations.
Testing gates enforced during upstream integration include regression, build, and targeted tests. The workflow drives deterministic subagents to execute these gates and coordinate independent reviewer approvals before accepting any ported upstream fix into otto-cli.
Yes, you can port critical fixes at scale without conflicts. The workflow enforces file-disjoint lanes and safety invariants, coordinating issue selection and testing gates to ensure experienced engineers can safely port multiple upstream fixes in parallel.
You should use deterministic lanes instead of manual cherry-picking to uphold safety invariants and ensure correct gating. Manual cherry-picking lacks the automated lane planning, testing gates, and integration reporting needed for safe, auditable upstream integrations.
berkcangumusisikLocate a commit by description or hash and cherry-pick it into the current branch.
yanet-platformOrchestrate branch creation, PR staging, CI gating, and merge workflows.
Matt-Aurora-VenturesDispatch fresh subagents to execute independent tasks from a plan.
Knuckles-TeamAutomate Git history fixes using rebase, cherry-pick, and bisect workflows.
