What problem does it solve?
Landing a confirmed, embargoed vm2 security fix from a private per-advisory fork into local main involves many error-prone manual steps: syncing the fork, resolving conflicts across CHANGELOG, ATTACKS.md, and lib code, scrubbing reporter attribution, and re-running the full multi-version test sweep. This Skill automates that integration while enforcing strict safety rules.
Core Features & Use Cases
- Deliberate conflict resolution: Handles CHANGELOG entry trimming, ATTACKS.md category renumbering, package.json version bumps, and semantic lib/*.js merges with diff3 context.
- Attribution scrubbing: Removes reporter names, handles, embargo dates, and acknowledgements from commits, comments, and docs before landing.
- Advisory metadata audit: Checks GHSA fields (CVSS vector, CWE, version ranges) via the GitHub API and proposes concrete values for missing items.
- Full test verification: Re-runs the test suite across Node versions 8 through 26 plus the advisory's own repro before reporting.
- Use Case: After a reporter confirms a sandbox escape fix on the private fork, invoke with the GHSA ID to land it as a single squashed commit on local main without ever pushing to origin.
Quick Start
Merge the confirmed fix for GHSA-9g8x-92q2-p28f into local main and run the full test sweep.