agentleFS
Sign inStart free
Marwan-Ahmed-devMarwan-Ahmed-dev/vibecode-pro-max/.claude/skills/vc-publish/SKILL.md

vc:publish

Skill0 starsChanged 3 months agoMITView on GitHub

Push agent harness improvements from the current development repo to the remote kit repository. Use when you want to publish local harness changes back to the shared kit. Diffs managed files, shows what changed, bumps version, and pushes.

  • Commits and pushes

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never modify the kit repo without user approval

    line 50
  2. Very specific:

    Never use --no-verify to skip hooks

    line 51
  3. Distinctive:

    Never widen scope beyond the resolved file sets

    line 52
  4. Distinctive:

    Never push if leak detection fails (Step 8)

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

vc-publish

Push harness improvements from the current development repo to the remote kit repository. This is the maintainer counterpart to vc-update.

  • vc-update = user pulls latest harness INTO their project FROM the remote
  • vc-publish = maintainer pushes improvements FROM the dev repo TO the remote

Codex Mirror Note

The .codex/agents/*.toml files are generated from .claude/agents/*.md by the build step build-codex-toml.mjs. Before publishing agent source changes, run:

node .claude/skills/vc-audit-vc/scripts/build-codex-toml.mjs

validate-agent-parity.mjs --strict rejects any hand-edited TOML — all TOML must be generated.

Prerequisites

  • Local checkout of the kit repo
  • Git push access to the remote

v3 (D3): .vc-publish-config is no longer a prerequisite. v3 diffs against the last git tag in the upstream kit repo; the legacy kitRepoPath config is preserved as a fallback for v2.x consumers.

Workflow (11 steps, see references/vc-publish.md for full contract)

  1. Load config — read .vc-publish-config (v2.x) or prompt for kit repo path (v3). Verify worktree is clean.
  2. Read manifest — extract version from vc-manifest.json in the kit repo.
  3. Resolve both file sets — run the kit repo's resolve-manifest.mjs --json against both roots. Extract files and kitOnly.
  4. Compute diff — additions, removals, modifications, strip (CLAUDE.md/AGENTS.md always flagged).
  5. Print summary — table of [modified] / [new] / [removed] / [strip] / [unchanged].
  6. STOP — confirm publish — show the summary, ask the user to confirm or modify. Never auto-publish.
  7. Apply changes — copy files from dev to kit repo, preserving executable bits on .cjs hooks. Run npm install in vc-mcp-management/scripts/ if changed.
  8. Leak detection — grep for vendor-stack references (flowser|tRPC|Prisma|Supabase|CloakBrowser|OpenClaw in v2.x; broader set in v3) against the dev repo. Zero matches expected for a portable kit.
  9. Commit + tag — git -C <kitRepoPath> add -A, then commit -m "publish v<version>", then tag v<version>. Never use --no-verify.
  10. Push — git -C <kitRepoPath> push origin main --tags.
  11. Print final summary — committed hash, tag, list of pushed files.

Strict Rules

  • STOP at Step 6 — never auto-publish, never skip the confirmation
  • Never modify the kit repo without user approval
  • Never use --no-verify to skip hooks
  • Never widen scope beyond the resolved file sets
  • Never push if leak detection fails (Step 8)

End every response with the subagent status block:

**Status:** DONE | DONE_WITH_CONCERNS | BLOCKED | NEEDS_CONTEXT
**Summary:** [1-2 sentence summary]
**Files modified:** [comma-separated list]
**Concerns/Blockers:** [if applicable]

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free