davesnx/setup/skill-vendor

Skill vendor

agents/skills/VENDOR lists each upstream repository, its branch, the directory that holds the skills there, the pinned commit, and the skills copied from it. The copies under agents/skills/ are the working copies. skill-vendor moves changes in either direction, only when asked.

Steps

1. Run skill-vendor check and read every line. Each skill is up to date,

upstream ahead, local ahead, new local, new upstream, diverged, or pending. Exit 1 means at least one skill needs a pull or push.

1. Pick the direction from those states and the user's request:

• Upstream moved and the user wants it: skill-vendor pull. It replaces the

local copies and records the new commit in VENDOR.

• Local edits go upstream: skill-vendor push -m "<message>" commits on the

upstream branch. For a pull request, add --branch <name>; the pin stays unchanged until that branch merges.

• diverged: stop and report. Both sides changed, and the user merges by

hand.

1. Run skill-vendor check again. Every listed skill reads up to date, or

local ahead for a branch push that is still open.

1. Commit agents/skills/VENDOR together with the skill copies it describes,

only when the user asks for a commit.

Rules

• pull refuses while a skill is local ahead, new local, or diverged.

pull --force discards those local edits; use it only when the user says so.

• push refuses while upstream is ahead. Pull first.
• A new skill also needs whatever the upstream repository asks for, such as a

README row or a plugin manifest entry. Push it on a branch and finish those by hand in the pull request.

• Clones live under ~/.cache/skill-vendor. A failed clone or fetch means the

machine lacks SSH access to the upstream. Report it; do not switch remotes.

Command details live in `terminal/bin/README.md`. After changing the command, run bash agents/skills/skill-vendor/tests/skill-vendor.sh.