vc-publish

Push harness improvements to a remote kit repository with version bumps.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/tutran27/trust-room-AI --skill vc-publish-tutran27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-publish
Source: https://github.com/tutran27/trust-room-AI/tree/main/.agents/skills/vc-publish
Command: npx skills add https://github.com/tutran27/trust-room-AI --skill vc-publish-tutran27

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, github-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of pushing harness improvements to a remote kit repository, managing version bumps, and ensuring portability of the harness across projects.

Core Features & Use Cases

  • Automated Publishing: Push harness improvements from a development repository to a remote kit repository.
  • Version Bumping: Automatically bump the version based on the type of changes (patch, minor, major).
  • Leak Detection: Checks for any project-specific content that should not be present in the kit repository.
  • Configuration Management: Reads configuration from a .vc-publish-config file to determine the kit repository path.
  • Use Case: Ideal for maintainers who need to update a shared kit repository with improvements from their development branch.

Quick Start

Run the vc-publish skill to publish your harness improvements to the remote kit repository.

Frequently Asked Questions about vc-publish

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

FAQPage Schema
How do I automate pushing harness improvements to a remote kit repository?

You can automate pushing harness improvements by running a publishing process that transfers changes from your local development checkout to a remote kit repository using Git for version control and release tracking.

How does version bumping work for remote kit repository updates?

Version bumping works by automatically evaluating your harness changes and incrementing the version number as a patch, minor, or major release before pushing the updates to the remote kit repository.

How do I detect project-specific content leaks before publishing shared harness updates?

To detect project-specific content leaks before publishing shared harness updates, the process scans your local checkout to identify and prevent project-specific content from contaminating the portable kit repository.

Do I need a local checkout of the kit repository to manage harness version bumps?

Yes, you need a local checkout of the kit repository and a configuration file named `.vc-publish-config` to designate the path and successfully execute the automated version bumping process.

Can I use GitHub CLI for harness publishing and release tracking?

Yes, you can use GitHub CLI alongside Git to manage release tracking and push harness improvements to the remote kit repository, ensuring portability across multiple projects.

What is the best way to maintain harness portability across projects during version control?

The best way to maintain harness portability during version control is to use an automated publishing process that checks for project-specific content leaks and manages version bumps before pushing to the remote repository.