Agent skill · laurigates
git-upstream-fix-check
Check upstream HEAD before patching vendored, tarball-installed, or forked code. Use when patching a dependency, custom node, or fork you don't own.
What it needs
About 2k tokens when loaded.
What this skill does
/git:upstream-fix-check Fires when you are about to edit third-party code inside the project — a path under vendor/, site-packages/, nodemodules/, customnodes/, thirdparty/, or a fork checkout. Every command below is GitHub-specific (gh); vendored code from GitLab/Codeberg/sourcehut has no recipe here. See git-plugin:gh-cli-agentic for the raw gh api contents command form, git-plugin:git-fork-workflow once you have confirmed upstream carries the fix, git-plugin:git-upstream-pr for the contribute-back handoff, and workflow-orchestration-plugin:workflow-verify-before-filing for the different case of a backlog of N accumulated bug candidates you are about to file. Before patching third-party code that lives inside the project (a custom ComfyUI node, a vendored library, a tarball-installed package, a fork checkout), check whether the bug is already fixed upstream. A 30-second gh lookup often replaces a 30-minute patch and a PR the maintainer will close as duplicate. Quick checks If the most recent push is months old and the issue tracker shows similar bug reports closed-without-merge, the project is effectively stale — patch locally and move on. If there's recent activity AND the file at master no longer matches the local copy, prefer upgrading the install over patching the snapshot. When this matters most Tarball-installed packs without .git. Common with package managers that snapshot rather than clone (ComfyUI-Manager, pip wheel installs, vendored deps, npm pack-style installs). Local version is pinned at install time and may be many releases behind, so the obvious bug may be obviously fixed upstream. Forks with diverged history. The bug may already be fixed on upstream main but never pulled into the fork. Check upstream before deciding whether to patch the fork or rebase it. Linter / formatter / generator output checked into the repo. Patching the output is usually wrong — find the generator's bug upstream instead. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills laurigates/git-upstream-fix-check