agentleFS
Sign inStart free
vibe-cokitvibe-cokit/claude-code/skills/vk-git-tag/SKILL.md

vk-git-tag

Skill1 starsChanged 4 months agoApache-2.0View on GitHub

⚡ Create an annotated git tag with a release message

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use git-manager agent with model: haiku to create an annotated tag following the Tag Workflow and Tag Message Standards defined in the …

    line 16
  2. Distinctive:

    When calling Task tool, you MUST specify:

    line 18
  3. Very specific:

    If {VERSION} is omitted, the agent determines the next SemVer bump from commits since the latest tag (feat → minor, fix/perf → patch, …

    line 28
  4. Very specific:

    Only push the tag if the user explicitly requests it (--push or keywords "push", "and push").

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Git Tag

Variables

VERSION: $1 (optional — e.g. v1.4.0. If omitted, auto-bump from latest tag using conventional commits) PUSH: $2 (optional — pass --push to push the tag to remote)

Workflow

Use git-manager agent with model: haiku to create an annotated tag following the Tag Workflow and Tag Message Standards defined in the agent.

When calling Task tool, you MUST specify:

model: haiku

Pass {VERSION} and {PUSH} to the agent.

Notes

  • If {VERSION} is omitted, the agent determines the next SemVer bump from commits since the latest tag (feat → minor, fix/perf → patch, BREAKING CHANGE / ! → major).
  • Tags MUST be annotated (git tag -a) with a release message body — never lightweight tags.
  • Tag message MUST follow the same rules as commits: no AI attribution, present-tense imperative summary.
  • Only push the tag if the user explicitly requests it (--push or keywords "push", "and push").

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