skillup tag¶

Create a <segment>--v<version> tag for the version currently in each segment's manifest.

skillup tag [--path <dir>] [--push --remote <url>]

--push takes its token from SKILLUP_TOKEN, never a flag.

Tags are decoration here¶

Nothing in skillup reads a tag. The baseline for every calculation comes from the git history of each segment's plugin.json, so a missing or late tag costs visibility and nothing else.

That is the opposite of a tag-baselined tool, where a forgotten tag silently corrupts the next version.

It tags where the version was set, not at HEAD¶

The commit at which each version last changed is already known — it is the same lookup the whole tool is built on — so the tag goes there. Tagging HEAD would attach the version to whatever merged most recently.

This also means a repository can be back-filled: run tag on a repository that has never been tagged and each version gets its tag at the right commit.

Interoperability¶

The format matches what claude plugin tag produces, so the two can be used against the same repository without owning rival namespaces.

Exit codes¶