skills.rest
eevennsoh
eevennsohCOMMUNITY
Explore all skills by this author →
GitHub

vpk-sync

Synchronize local VPK prototypes with upstream repositories via merge or rebase.

Updated Aug 23, 2026
Search Tags:#git#push#sync#pull#contribute#vpk
One-click install
npx skills add https://github.com/eevennsoh/VPK --skill vpk-sync
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vpk-sync
Source: https://github.com/eevennsoh/VPK/tree/main/.cursor/skills/vpk-sync
Command: npx skills add https://github.com/eevennsoh/VPK --skill vpk-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Keeps a local VPK prototype aligned with the upstream kit, simplifying updates and enabling contributions back to upstream without drift.

Core Features & Use Cases

  • Supports init, pull, push, sync, and contribute workflows against upstream VPK
  • Allows merge or rebase strategies, path filtering, and optional fork-based PRs to upstream
  • Handles common failure modes (unconfigured upstream, unrelated histories, conflicts) with guidance and automated options

Quick Start

Run the vpk-sync command to begin an interactive sync flow and follow the prompts.

Frequently Asked Questions about vpk-sync

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

FAQPage Schema
How do I sync my local VPK prototype with the upstream repository?▼

To sync your local VPK prototype with the upstream repository, run the vpk-sync command to begin an interactive flow that pulls updates and aligns your changes. It handles path filtering and guards against unrelated histories.

What is the best way to contribute back to the VPK upstream from a fork?▼

The best way to contribute back to VPK upstream from a fork is using the contribute workflow, which supports optional fork-based PRs via gh. It guides you through pushing pull requests while preventing credential leakage.

Can I use a rebase strategy instead of merge when pulling upstream VPK updates?▼

Yes, you can use a rebase strategy instead of merge when pulling upstream VPK updates. The sync workflow explicitly supports both merge and rebase strategies to integrate changes while keeping your history clean.

Do I need git and gh installed to run the VPK sync workflow?▼

Yes, you need both git and gh installed to run the VPK sync workflow. These dependencies are required for executing scripts that initialize upstream, pull updates, and push pull requests for contributions.

Why does pulling VPK upstream changes fail with unrelated histories?▼

Pulling VPK upstream changes fails with unrelated histories when your local repository lacks a proper upstream configuration. The sync tool guards against this by handling unconfigured upstreams and providing automated options to resolve conflicts.

Related Skills

Explore More Software Engineering Skills→
Strategic-AutomationStrategic-Automation
6

github-auth

Configure GitHub authentication via HTTPS tokens, SSH keys, or gh CLI.

Official
Intermediate
codacy-open-source-projects-scanscodacy-open-source-projects-scans
1

fix-sync

Resolve merge conflicts in ClickHouse sync pull requests using the gh CLI.

Official
Advanced
JeremyDev87JeremyDev87
31

git-master

Enforce atomic commits and conventional messages for clean Git histories.

Community
Advanced
chiptoe-svgchiptoe-svg

update-skills

Detect and merge upstream updates for git branch-distributed skills.

Community
Intermediate