skills.rest
cryborg1211
cryborg1211COMMUNITY
Explore all skills by this author →
GitHub

vc:publish

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

Updated May 10, 2026
Search Tags:#publish#diff#resolver#harness#version-bump#kit-repo
One-click install
npx skills add https://github.com/cryborg1211/quant_trading_telegram_bot --skill vc-publish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vc:publish
Source: https://github.com/cryborg1211/quant_trading_telegram_bot/tree/main/.agents/skills/vc-publish
Command: npx skills add https://github.com/cryborg1211/quant_trading_telegram_bot --skill vc-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of propagating harness improvements from the development repository to the remote kit repository. It coordinates configuration checks, manifest handling, and governance steps to ensure changes are safely prepared for sharing.

Core Features & Use Cases

  • Resolver-driven diffing to identify new, modified, and removed files between dev and kit repos.
  • Harness-only CLAUDE.md/AGENTS.md transformation to strip project-specific context before publishing.
  • Automated version bump and git tagging as part of the publish cycle.
  • Leak-detection gating to prevent leakage of non-harness content during publish.

Quick Start

Run vc-publish from the root of the development repository to begin the publish cycle.

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 from a dev repository to a kit repo?▼

Publishing harness changes requires a local kit checkout containing vc-manifest.json and a clean git worktree to safely run the resolver-driven diff and apply content transformations.

How does leak detection work when publishing harness files?▼

Leak-detection gating prevents non-harness content from publishing by stripping project-specific context from CLAUDE.md and AGENTS.md files, ensuring only harness rules propagate to the kit repository.

Does publishing kit manifest changes require a clean worktree?▼

Yes, publishing requires a clean worktree and a local kit checkout containing vc-manifest.json to execute version bumps and apply harness-only CLAUDE.md transformations safely.

What is the best way to diff a development repository against a kit repository?▼

Resolver-driven diffing identifies new, modified, and removed files between dev and kit repos, applying harness-only content rules to isolate sharable configuration from project-specific code.

Why does publishing fail when project-specific content is in CLAUDE.md?▼

Publishing fails because leak-detection gating blocks non-harness content, requiring CLAUDE.md and AGENTS.md transformations to strip project-specific context before propagating to the kit repo.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
tutran27tutran27

vc-publish

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

Community
Advanced
dtbuchholzdtbuchholz

review-and-fix

Reviews current code changes with git diffing and applies fixes.

Community
Advanced
usepowershellusepowershell
9

speckit-constitution

Populate constitution templates with concrete principle values and sync related files.

Community
Advanced