skill git - version control for your skills

Manage AI agent skills with version control to initialize tracking, commit changes with semantic versioning, and revert to previous skill versions.

Security Scan

The skill's behavior is consistent with a local 'version control for skills' tool, but there are a few small implementation/metadata gaps you should be aware of before running it.

Purpose & Capability

The name/description (version control for skills: init, commit, revert, scan, merge, check) match the actions the SKILL.md describes: creating git repos, committing, tagging, reverting, scanning skill markdown, and synthesizing merges. The commands operate on local skill folders and update a local ~/.skill-git/config.json — that aligns with the stated purpose. Minor note: the skill claims no required binaries in the registry metadata, but the runtime instructions explicitly require git and jq.

Instruction Scope

Instructions are detailed and confined to the stated domain: they read SKILL.md and other top-level *.md files, extract rules, run git operations (init/commit/reset/tag/diff), manipulate a local ~/.skill-git cache and config, and prompt the user for destructive actions. They also auto-detect agent via parent process and config files. The tool reads many local config files and may read untracked file contents only with explicit user consent; sensitive filename blocklists are applied in many places. Overall, the steps stay within the version-control/analysis scope.

Install Mechanism

There is no remote install or downloader; this is an instruction-only skill with one included script (scripts/sg-init.sh) that will be executed locally. No external URLs or archive extraction are used. The primary install risk is running the included shell script on the user's machine — you should review its content before execution (it is present in the bundle).

Credentials

The skill does not declare required environment variables in the registry, but the runtime docs require git and jq and reference environment context variables (e.g., CLAUDE_PLUGIN_ROOT, $ARGUMENTS, $PPID). The tool reads and writes many local files under ~/.skill-git and user agent directories (~/.claude, ~/.gemini, ~/.openclaw, etc.). It does not request external API keys or unrelated credentials. The omission of declared binaries/vars is a metadata mismatch but not a functional mismatch with purpose.

Persistence & Privilege

The skill is not always-on and runs only when invoked. It writes to ~/.skill-git (config, cache), may create .git folders and perform git init/commit/tag/reset operations inside users' skill directories, and can copy backups to /tmp. Those privileges are necessary for a local VCS tool, but you should expect it to modify your skill folders and config.json when you confirm operations. Autonomous invocation is allowed by platform default but not an additional flagged privilege.

Assessment

This skill appears to do what it says: local version control and merging of skill folders. Before using it, review these points: (1) The SKILL.md expects git and jq but the registry metadata does not list them — install git and jq first. (2) Inspect scripts/sg-init.sh (included in the bundle) before running the init command — it will be executed by the skill. (3) The tool will create .git repositories, perform commits/tags/resets, and may delete tags during reverts; destructive actions require explicit confirmation but will modify your skill folders and ~/.skill-git/config.json. Back up your skills (or let the tool create the /tmp backup) before performing multi-version reverts or merges. (4) The skill reads many local config and plugin files and may read untracked file contents only if you consent; sensitive filenames are blocklisted in many places but double-check for secrets in your skill folders. If those behaviors are acceptable, this skill is coherent with its stated purpose.

skill-git is a version control system for AI agent skills. It gives each skill folder its own independent git history, tagged with semantic versions (v1.0.0, v1.1.0, …), so you can commit snapshots and revert to any previous version at any time.

Six commands are available:

• init — set up version tracking for all skills under an agent directory
• commit — snapshot changed skills with a version bump and commit message
• revert — roll back one or more skills to a previous version
• check — check a skill for internal rule conflicts, agent config conflicts, and security issues
• scan — scan registered skills for semantic overlap and get merge suggestions
• merge — merge two or more similar skills into one stronger, more complete skill

Prerequisites

Before using any command, ensure these tools are installed:

• git — git --version (install: brew install git on macOS, apt install git on Linux)
• jq — jq --version (install: brew install jq on macOS, apt install jq on Linux)

The init command will check for git automatically. If jq is missing, commit and revert will fail when updating config.json.

Intent Routing

Parse $ARGUMENTS. If $ARGUMENTS is empty, infer intent from the user's natural language message.

Trigger	Action
init / "initialize" / "set up" / "track my skills" / "start tracking"	Read $CLAW_SKILL_DIR/init.md and follow it exactly
commit / "save" / "snapshot" / "new version" / "save skill changes"	Read $CLAW_SKILL_DIR/commit.md and follow it exactly
revert / "roll back" / "undo" / "restore" / "go back to"	Read $CLAW_SKILL_DIR/revert.md and follow it exactly
check / "check skill" / "validate skill" / "find conflicts" / "skill conflicts"	Read $CLAW_SKILL_DIR/check.md and follow it exactly
scan / "scan skills" / "find overlapping skills" / "which skills can I merge"	Read $CLAW_SKILL_DIR/scan.md and follow it exactly
merge / "merge skills" / "combine skills" / "consolidate skills"	Read $CLAW_SKILL_DIR/merge.md and follow it exactly
No args or ambiguous intent	Show the menu below and wait for user input

Menu (show only when intent is unclear)

skill-git — version control for your AI skills

Available commands:

  1. init      Set up version tracking for your skills
  2. commit    Snapshot changed skills with a new version
  3. revert    Roll back a skill to a previous version
  4. check     Check a skill for conflicts and security issues
  5. scan      Scan all skills for overlap and merge candidates
  6. merge     Merge two or more similar skills into one

Which would you like to run? (enter a number, name, or describe what you want)

Wait for the user's response, then route to the appropriate .md file above.

Asset Skills

The check, scan, and merge commands depend on two internal library skills located in assets/:

• assets/rule-extraction/SKILL.md — extracts structured rule lists from skill markdown files
• assets/conflict-patterns/SKILL.md — detects conflicts between two rule lists (direct contradiction, semantic contradiction, overlap, security patterns)