vc-publish

Publishes harness improvements from a development repo to the remote kit repository with diffing, versioning, and leak detection.

2|Updated Sep 15, 2025
One-click install
npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-publish-marsley01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-publish
Source: https://github.com/marsley01/Marsley-Portfolio-Web/tree/main/.agents/skills/vc-publish
Command: npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-publish-marsley01

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Maintainers of the vibecode-pro-max-kit harness need a safe, repeatable way to push improvements from their development repo to the remote kit repo without leaking project-specific content or skipping version bookkeeping. This Skill automates the diff, version bump, leak detection, commit, tag, push, and GitHub Release steps. ## Core Features & Use Cases - Resolver-driven diffing: Computes added, modified, deleted, and preserved files between the dev repo and kit repo using resolve-manifest.mjs and compute-sync-plan.mjs. - Leak detection gate: Scans the full shipped text surface for product names, absolute paths, and dangling context references, reverting changes if any leak is found. - Controlled release flow: Enforces two separate user confirmations (publish confirm and explicit push approval), bumps semver in vc-manifest.json, syncs the legacyDeletions ledger, creates a git tag, and publishes a GitHub Release. - Use Case: After adding a new skill and fixing a hook in the dev repo, run vc-publish to review the diff, bump the minor version, verify no project content leaks, and push v2.2.0 to the remote kit repo. ## Quick Start Ask the AI to publish the current harness improvements to the kit repo using the vc-publish skill and confirm the version bump type when prompted.

Frequently Asked Questions about vc-publish

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

FAQPage Schema
How do I publish harness changes to the vibecode-pro-max-kit repo?

Run the vc-publish skill with a .vc-publish-config file pointing to your local kit repo checkout. It computes the diff via compute-sync-plan.mjs, shows a summary, asks for a version bump type, runs leak detection, then commits, tags, and pushes after your explicit approval.

What is the difference between vc-publish and vc-update?

vc-update is the user-side skill that pulls the latest harness into a project from the remote kit repo. vc-publish is the maintainer counterpart that pushes improvements from the development repo to the remote kit repo.

How does vc-publish prevent project-specific content from leaking?

It runs a resolved-set leak detection gate that greps the shipped text files for product names, absolute paths like /Users/, and dangling process/context references. If any match is found, it reverts the kit worktree and stops before committing.

Does vc-publish push to the remote automatically?

No. It requires two separate confirmations: one to approve the publish after the diff summary, and a second explicit 'push' approval after the commit and tag are created locally. The push never runs without that second confirmation.

How are version bumps decided when publishing the kit?

The user chooses patch, minor, or major at the confirmation step. Patch covers hook fixes and doc updates, minor covers new skills or agents, and major covers CLAUDE.md structure or manifest schema changes. If the kit version already matches the target, the bump is skipped.

Why does vc-publish not copy the dev repo's CLAUDE.md directly?

The dev repo's CLAUDE.md and AGENTS.md contain project-specific details like tech stacks, feature lists, and absolute paths. The skill applies only methodology changes to the kit's harness-only versions and strips all project-specific content before publishing.