skills.rest
withkynam
withkynamCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

vc-publish

Publish harness improvements from the development repository to the remote kit repository.

1.1k|223|Updated May 27, 2026
Search Tags:#automation#git#workflow#publish#manifest#diff#kit
One-click install
npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-publish-withkynam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vc-publish
Source: https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-publish
Command: npx skills add https://github.com/withkynam/vibecode-pro-max-kit --skill vc-publish-withkynam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pushes harness improvements from the development repository to the remote vibecode-pro-max-kit kit repository. This keeps the kit aligned with development changes, enables diff-based publishing, and ensures version bumps and pushes happen in a controlled, auditable manner.

Core Features & Use Cases

  • Diff development vs. kit repos to identify changes that should be published
  • Bump vc-manifest.json version on publish to reflect new kit state
  • Push updated harness files to the remote kit repository
  • Serve as maintainer counterpart to vc-update, coordinating remote-kit improvements

Quick Start

Configure the kit repo path via .vc-publish-config and run the vc-publish workflow to publish harness updates.

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 updates from my development repository to a remote git kit repo?▼

You can publish harness updates by running a config-driven workflow that computes diffs, validates the working tree, bumps the manifest version, and pushes changes to the remote kit repository in a safe, auditable sequence.

How do I diff development files against a remote kit repository before pushing changes?▼

Diffing development files against a remote kit repository identifies harness improvements that should be published, ensuring only validated changes are pushed during the publish workflow.

Do I need a specific configuration file to automate pushing workflow changes to a manifest-based git repository?▼

Yes, you need to configure the kit repository path via a .vc-publish-config file before running the workflow to publish harness updates safely.

What is the best way to keep a shared code kit aligned with local development changes?▼

Using a maintainer workflow that bumps the manifest version and pushes validated harness diffs to the remote repository keeps the shared kit aligned with development changes in an auditable manner.

Can I use this publish workflow to coordinate improvements with a counterpart update process?▼

Yes, this workflow serves as the maintainer counterpart to an update process, coordinating remote kit improvements by pushing development changes that the update process later pulls into projects.

Why does publishing workflow changes require bumping the manifest version?▼

Bumping the manifest version on publish reflects the new kit state, ensuring that downstream updates and version tracking remain accurate when harness files are pushed to the remote repository.

Related Skills

Explore More Software Engineering Skills→
cryborg1211cryborg1211

vc:publish

Publishes harness changes from the development repository to the kit repository.

Community
Advanced
lovecrushfamilylovecrushfamily
1

vc-update

Compare local harness versions with a remote kit repository and apply updates after dry-run confirmation.

Community
Advanced
wewetv1987-cellwewetv1987-cell

git-helper

Manage Git repository status, pull, push, branch, and log operations.

Community
Basic
sabertazimisabertazimi

generating-commits

Generate Conventional Commits messages and commit staged changes.

Community
Advanced