{
  "markdown": "# claude-code-plugin-gvt-dev\n\nThe **`gvt-dev` plugin** for Claude Code — shared skills, agents, and hooks used across Genvid game projects.\n\nThe plugin provides workflows for git (`commit-changes`, `create-pr`, `rebase-branch`, `rebase-stack`, `split-branch`, `clear-worktree`), planning (`plan-task` with an analyst → designer → planner pipeline), backlog grooming (`triage-issues`, `plan-next-issue`), decision records (`create-adr`), validation, code review, session retrospectives, convention auditing, plugin releasing (`release-plugin`, `reconcile-mcp-pin`), and npm package releasing (`release-npm-package`).\n\nIt is distributed through the [`claude-code-gvt-marketplace`](https://github.com/GenvidTechnologies/claude-code-gvt-marketplace) catalog (marketplace name `gvt-plugins`).\n\n## Install\n\n```text\n/plugin marketplace add https://github.com/GenvidTechnologies/claude-code-gvt-marketplace.git\n/plugin install gvt-dev@gvt-plugins\n```\n\nAfter installing, run the audit:\n\n```text\n/gvt-dev:audit-conventions\n```\n\nThe audit reports whether the repo satisfies the plugin's [convention contract](plugin/CONVENTIONS.md) — what files and config keys the installed skills and agents expect.\n\nFor a greenfield repo or a legacy setup migrating from the old template-rendered system, run with `--fix` (see [Migration](#migrating-from-the-legacy-template-rendered-setup) below).\n\n## What the plugin provides\n\n**Skills** (invoked as `/gvt-dev:<name>`):\n\n| Skill | Purpose |\n|-------|---------|\n| `commit-changes` | Create a git commit following the project's CLAUDE.md format |\n| `create-pr` | Open a PR (GitHub via `gh`, Bitbucket via copy-paste link) |\n| `plan-task` | Analysis → design → planning pipeline with user checkpoints |\n| `plan-next-issue` | Pick the next backlog issue and route it into `plan-task` (optionally triages first) |\n| `triage-issues` | Triage an issue backlog — dedup, enrich, link dependencies, split, stamp `triaged` |\n| `create-adr` | Add or chronologically insert an Architecture Decision Record |\n| `validate-changes` | Dispatch the validator agent on the project's full validation suite |\n| `rebase-branch` | Rebase a feature branch with conflict resolution guidance |\n| `rebase-stack` | Rebase a stacked branch after an earlier branch was squash-merged |\n| `split-branch` | Split a large branch into reviewable stacked branches |\n| `clear-worktree` | Tear down a git worktree safely, recovering unpushed work and worktree-keyed memory |\n| `run-retro` | Session retrospective — proposes doc / skill / agent improvements |\n| `sync-config` | Wraps `/plugin update gvt-dev` + audit re-run |\n| `cleanup-initiative` | Close out an initiative folder (optional convention) |\n| `condense-lessons` | Extract reusable insights from a lessons-learned doc |\n| `publish-npm-package` | Set up a package to publish on npmjs via OIDC trusted publishing |\n| `release-plugin` | Cut a plugin release — bump, tag, and bump the marketplace `source.ref` |\n| `release-npm-package` | Cut a routine npm package release — bump, tag, and trigger the OIDC publish workflow |\n| `reconcile-mcp-pin` | Reconcile agent tool inventories after a bundled MCP server pin bump / scope rename |\n| `migrate-cordova-ci` | Migrate a Cordova plugin's CI from CircleCI to GitHub Actions |\n| `audit-conventions` | Validate / migrate against the convention contract |\n| `maintain-wiki` | Maintain a project's LLM-wiki compounding-memory knowledge base (ingest / query / lint) |\n| `build-probe` | Build a throwaway probe to answer one checkable question, then promote or discard |\n\n**Agents** (dispatched via `subagent_type: \"gvt-dev:<name>\"`):\n\n`analyst`, `designer`, `planner`, `tech-writer`, `ts-implementer`, `validator`, `code-reviewer`, `issue-triage-analyst`, `wiki-librarian`.\n\n**Hook:** `pre-commit-lint` runs `commands.lint` from `.gvt-agent.json` before every `git commit` in the Bash tool.\n\n**Complementary official plugins:** gvt-dev stays focused on project-aware workflows and intentionally does *not* reimplement generic tooling. For standalone PR review use Anthropic's `/code-review` command (its `code-review` plugin); for quality-only refactor passes use the `code-simplifier` agent. The in-pipeline `gvt-dev:code-reviewer` agent is scoped to the `plan-task` review gate, not full PR review.\n\n## The convention contract\n\nThe plugin reads project context from four files in the consuming repo, in a contract documented at [`CONVENTIONS.md`](plugin/CONVENTIONS.md):\n\n| File | Purpose |\n|------|---------|\n| `CLAUDE.md` | Project context, imports `@CONVENTIONS.md` |\n| `CONVENTIONS.md` | Copy of the plugin's canonical contract, synced by `/gvt-dev:audit-conventions --fix` |\n| `docs/TOC.md` | Documentation index |\n| `.gvt-agent.json` | Capability registry — project name, commands, repo overrides, feature flags |\n\nEvery skill and agent self-declares its expectations under `metadata.expects` in its YAML frontmatter — paths, config keys, and tools it needs. The `audit-conventions` skill walks these declarations and reports any unmet expectations against the consuming repo.\n\n## Migrating from the legacy template-rendered setup\n\nIf your repo currently has a `burbank-claude-config` git submodule and a `claude-config.json` file at the root, run:\n\n```text\n/gvt-dev:audit-conventions --fix\n```\n\nThe audit will print a dry-run summary of the migration: translating `claude-config.json` → `.gvt-agent.json`, adding the `@CONVENTIONS.md` import to `CLAUDE.md`, copying `CONVENTIONS.md` to the repo root, deleting rendered `.claude/` files (only files carrying the `AUTO-GENERATED` marker — user-edited files are kept and surfaced as SKIPPED notes), and removing the submodule.\n\nReview the plan, then run:\n\n```text\n/gvt-dev:audit-conventions --fix --apply\n```\n\nThe migration script's `--apply` step refuses to run on a dirty working tree and doesn't auto-commit (the dry-run previews safely on a dirty tree). After it runs, review `git status` / `git diff` and commit.\n\n## Forking and adapting\n\nThe plugin is intentionally generic — it carries workflows, not project-specific content. If your org needs different conventions, fork the repo and edit the skill bodies directly. The `CONVENTIONS.md` schema is small on purpose; new feature flags or paths can be added there for non-inferable team practices.\n\n## Contributing\n\nDevelopment guide in [`CLAUDE.md`](CLAUDE.md). Highlights:\n\n- The plugin lives under `plugin/`; skills are directories with `SKILL.md`; agents are flat `.md` files in `plugin/agents/`.\n- Top-level frontmatter is fixed (`name`, `description`, plus the Anthropic-supported fields); custom expectations go under `metadata`.\n- Verb-noun skill names avoid collisions with built-in Claude Code skills.\n- Validate with `claude plugin validate plugin`.\n- Test `audit-conventions` with `node --test plugin/skills/audit-conventions/scripts/test/*.test.mjs`.\n- Commits in this repo use scope-based freeform messages — no ticket prefix.\n",
  "bytes": 6944,
  "sha": "ca1434475ca708dea9db8b04756cca1ec1da44d83d6730b03669d64dd54a81b3",
  "repo_slug": "genvidtechnologies/claude-code-plugin-gvt-dev",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/okf_genvidtechnologies_claude_code_plugin_gv_349bfe59/readme"
}