skills.rest
jimeh
jimehCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

hucode-upgrade-vscode

Replay Hucode patches onto a new upstream VS Code release branch.

Updated Apr 14, 2026
Search Tags:#git#vscode#conflict resolution#upgrade#cherry-pick#ci validation#fork maintenance
One-click install
npx skills add https://github.com/jimeh/hucode --skill hucode-upgrade-vscode-jimeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hucode-upgrade-vscode
Source: https://github.com/jimeh/hucode/tree/main/.agents/skills/hucode-upgrade-vscode
Command: npx skills add https://github.com/jimeh/hucode --skill hucode-upgrade-vscode-jimeh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Upgrading a VS Code fork to a new upstream release is error-prone: patch series must be compacted, cherry-picked onto a clean baseline, conflicts resolved against changed upstream APIs, and the result validated against CI. This Skill provides a disciplined, step-by-step procedure for performing that upgrade on the Hucode fork without losing commits, pushing broken branches, or missing silent runtime regressions. ## Core Features & Use Cases - Replay branch compaction: Rebuilds the previous series as curated topic commits that are tree-equivalent to the old series, with explicit decision notes and disqualifying-commit rules. - Baseline and series branch management: Creates upstream-<version> and series-<version> branches, resolves the microsoft/vscode remote by URL, and enforces safe push ordering so CI runs the right workflows. - Conflict scouting and resolution: Surfaces file overlap, modify/delete conflicts, and workflow changes before cherry-picking, with rules for adapting Hucode patches to new upstream APIs. - Validation and smoke testing: Runs provenance checks, compile, build-package tests, entrypoint drift checks, and Omni startup smoke tests, plus exact-head CI verification before moving the default branch. - Use Case: When VS Code 1.122.0 ships, use this Skill to compact the 1.121.0 Hucode series into replay topics, cherry-pick them onto the new tag, resolve conflicts, and publish a validated series-1.122.0 branch. ## Quick Start Use the hucode-upgrade-vscode skill to upgrade Hucode from the current series to VS Code release tag 1.122.0 and validate the result.

Frequently Asked Questions about hucode-upgrade-vscode

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

FAQPage Schema
How do I upgrade a VS Code fork to a new upstream release?▼

Fetch the upstream release tag, create a clean upstream-<version> baseline branch, compact your existing patch series into a replay branch of topic commits, then cherry-pick that stack onto a new series-<version> branch and resolve conflicts against the new upstream APIs.

How do I resolve cherry-pick conflicts when rebasing patches onto a new VS Code version?▼

Scout the conflict surface first by intersecting files changed by your patch stack with files changed in the upstream delta. Resolve commit-by-commit using the new upstream code as the base, preserve upstream API and lifecycle changes, and adapt your fork's behavior to them.

Why does git cherry-pick silently drop a commit during a long replay?▼

A pick can fail for environmental reasons like a stale index.lock, and cherry-pick --continue may resume at the next todo entry without applying it. Verify completeness afterward by comparing commit counts and running git range-diff between the old replay stack and the new series.

Can I run Git operations when the host does not have git-lfs installed?▼

Yes, but only when the new commits contain no LFS-managed content. Disable LFS filters with -c filter.lfs.process= and related config flags for pointer-only operations, and set GIT_LFS_SKIP_PUSH=1 for pushes; otherwise install git-lfs and publish the objects.

When should I push the new series branch to origin?▼

Push only after the replayed patch stack, compatibility fixes, validation updates, and the baseline changelog fragment are committed. Pushing earlier makes GitHub run upstream VS Code CI workflows instead of the fork's customized set, wasting CI minutes on failures.

Related Skills

Explore More Software Engineering Skills→
devemberxdevemberx
12

deploy

Automate guarded software releases with version bumps, git commits, tags, and package publication.

Community
Advanced
StringKeStringKe
6

release

Automate Cloudflare-Operator release workflows with version bumps, changelogs, Git tags, and GitHub releases.

Community
Advanced
cogni-workcogni-work
12

audit-copywriter

Audit arc-preservation alignment between cogni-narrative and cogni-copywriting pipelines.

Official
Advanced
storjstorj
3.3k

point-release

Creates Storj point releases by cherry-picking commits onto release branches and tagging versions.

Official
Intermediate