AGENT SKILL

claude-vm-apply-remote

Push a claude-vm guest worktree's committed changes to the remote, for a given run id (or the most recent run). Pushes only with explicit approval; never force-pushes.

License 许可
GPL-3.0
最近更新
2026-11-14
Stars
★ 0
Forks
0

01 前言 Front Matter

name
claude-vm-apply-remote
description
Push a claude-vm guest worktree's committed changes to the remote, for a given run id (or the most recent run). Pushes only with explicit approval; never force-pushes.

03 SKILL.md 正文

claude-vm-apply-remote

Push the changes a claude-vm guest committed (in its persistent worktree) to the remote. Use this when you want the guest's work to land on a remote branch directly, without first mirroring it onto the local source.

This skill pushes to the remote, so pushing requires explicit approval — show the commits and target branch, ask, and wait for a clear yes before pushing. Never force-push.

How runs are located

Same as /claude-vm-diff: each run writes $CLAUDE_VM_RUNS_DIR/<runid>/run.meta recording run_id, repo_src, repo_mount, worktree, and copy_back, and this repo's runs are the ones whose repo_src names it. The run dir persists after the guest exits (clone mode). bin/claude-vm-cleanup never removes a run's worktree/ or run.meta, so a run it has reaped is still found.

Inputs

  • <runid> (optional): the run to push. Defaults to the most recent run of this repo, selected the way /claude-vm-diff selects it.
  • <repo> (optional): the source repo root. Defaults to the current repo.
  • <branch> (optional): the remote branch to push to. When omitted, derive a descriptive branch name (e.g. claude-vm/<runid>); do not push to the default branch implicitly.

Steps

  1. Resolve the run dir and read run.meta (see /claude-vm-diff). If no recorded run exists, report and stop.

  2. Confirm repo_mount is clone — the worktree (a --no-hardlinks clone of the source) carries the guest's commits and its own origin pointing at the source. For a live run there is no separate worktree; report and stop.

  3. Show what would be pushed:

    git -C "<worktree>" --no-pager log --oneline "<base>..HEAD"
    git -C "<worktree>" --no-pager diff --stat "<base>..HEAD"
    

    If the worktree has uncommitted changes, the guest's work was not committed — report that and stop (there is nothing to push). The user can commit inside the worktree, or apply locally and commit there.

  4. Get explicit approval for the push, naming the target remote and branch. Wait for a clear "yes" / "push".

  5. Push the worktree's branch to the remote. The worktree's origin is the local source; to reach the true upstream, add/resolve the source repo's origin remote URL and push there, e.g.:

    upstream="$(git -C "<repo_src>" remote get-url origin)"
    git -C "<worktree>" push "$upstream" "HEAD:<branch>"
    

    Use a normal (non-force) push. If the remote rejects it (non-fast-forward), report the rejection and stop — do not force-push.

  6. Report the pushed branch and, if applicable, suggest opening a PR.

Notes

  • This skill only pushes committed work. If the guest's changes are uncommitted in the worktree, commit them (inside the worktree) or use /claude-vm-apply-local first.
  • Never force-push. A rejected push is surfaced to the user, who decides how to reconcile.

04 同仓库更多 Skills

TheVoskamps
TheVoskamps/claude-plugins-marketplace

mask-inappropriate-language

Replace inappropriate language (profanity, slurs, strong insults) in provided text or a file with asterisks, character-for-character, preserving everything else.

★ 0
TheVoskamps
TheVoskamps/claude-plugins-marketplace

theorem-agents-interface

The interface between the sdlc reviewer and the theorem agents it spawns — what each double-dash brief parameter means, and what each consequence class means. Preloaded into every theorem agent (sdlc:theorem-generator, the disprover, and the verifier) via its skills frontmatter, and read by name by the sdlc:theorem-based-pr-reviewer agent for what its briefs' parameters mean; not invoked from the user's slash menu.

★ 0
TheVoskamps
TheVoskamps/claude-plugins-marketplace

sdlc-config-user

Interactively create or merge-update the repo user sdlc config, `<repo-root>/.sdlc/user-config.yml` (tier 3 — this user, this repo, never committed), and add it to the repo's tracked `.gitignore`.

★ 0
TheVoskamps
TheVoskamps/claude-plugins-marketplace

sdlc-config-repo

Interactively create or merge-update the shared repo sdlc config, `<repo-root>/.sdlc/repo-config.yml` (tier 2 — tracked, every user of this repo).

★ 0
TheVoskamps
TheVoskamps/claude-plugins-marketplace

sdlc-config-global

Interactively create or merge-update the global user sdlc config, `$XDG_CONFIG_HOME/sdlc/user-config.yml` (tier 1 — this user, every repo on this machine).

★ 0
TheVoskamps
TheVoskamps/claude-plugins-marketplace

pr-read-cli-interface

The contract for sdlc's PR-read CLIs — sdlc-pr-round, sdlc-pr-adjustments, sdlc-fixer-brief and sdlc-records-chain — their arguments, exit codes and output grammar. Preloaded into sdlc:theorem-based-pr-reviewer, sdlc:issue-fixer, sdlc:docs-writer and sdlc:pr-finalizer via their skills frontmatter; not invoked from the user's slash menu.

★ 0