Standard Tooling Plugin

Claude Code plugin for the vergil-tooling ecosystem. Delivers shared hooks, skills, and agents to all managed repositories.

Overview

This plugin is the behavioral counterpart to the vergil-tooling Python package. While vergil-tooling provides runtime CLI tools (vrg-commit, vrg-submit-pr, etc.) via PATH, this plugin provides Claude Code configuration that enforces workflow compliance mechanically.

What's Included

Component	Purpose
Hooks	Pre/PostToolUse/Stop workflow guardrails
Skills	Shared workflow skills (commit, PR, etc.)
Agents	Bootstrap subagent for session context

Two-Repo Model

Repo	Delivers	Distribution
vergil-tooling	Python CLIs (st-*), validators	PATH
vergil-claude-plugin	Hooks, skills, agents	Claude Code plugin

These are complementary: the plugin tells Claude how to behave; PATH makes the tools available to run.

Installation

From marketplace

The plugin ships through a single channel, the floating v2.1 rolling tag: each release moves v2.1 forward, and a rollback with vrg-promote, a human-gated release act, moves it back to an earlier release (see the spec). It is installed per user: add the marketplace definition and the plugin enable to your user-level ~/.claude/settings.json, and the enable installs the plugin. If that file already has extraKnownMarketplaces or enabledPlugins objects, merge these entries into them rather than adding a second copy of either key:

{
  "extraKnownMarketplaces": {
    "vergil-marketplace": {
      "source": {
        "source": "github",
        "repo": "vergil-project/vergil-claude-plugin",
        "ref": "v2.1"
      }
    }
  },
  "enabledPlugins": {
    "vergil@vergil-marketplace": true
  }
}

Already registered vergil-marketplace at another ref? Editing the ref is a change of source, not an update: a marketplace update alone keeps the old registration. Follow vergil-tooling's Switching an existing machine procedure instead.

Do not put the marketplace definition in a repo's .claude/settings.json. A managed repo's file comes from the vergil-tooling template, which only enables vergil@vergil-marketplace: a second vergil-marketplace definition there would replace the user-level entry whole, and the nightly config audit requires the repo file to equal the template. See vergil-tooling's Claude Config Ownership model and Consuming Repo Setup.

Updating

A machine picks up a release, or a rollback, when its plugins are next updated. Run vrg-host plugins for the host and vrg-vm update --all for every running agent VM, in a human shell, then restart Claude Code. Both commands refresh the marketplace and the installed plugins and verify the registered repo and ref, and both refuse an agent identity. The ref is v2.1 before and after, so that check does not prove a machine moved. vrg-vm update --all skips a VM that is not running. The plugin README's Update section gives the full procedure and how to verify the installed version.

Local development

claude --plugin-dir /path/to/vergil-claude-plugin

Plugin Namespace

All skills are namespaced under vergil:

/vergil:<skill-name>