Wiki Index
Bundle OKF 0.2 · 2 conceitos · GenvidTechnologies/claude-code-plugin-gvt-dev
Open source Repository Open in the app JSON README (API)
About
# Wiki Index
This is the wiki's table of contents — every page under `wiki/`, grouped
under section headings, one line each. `/gvt-dev:maintain-wiki` keeps this
list current: a new page is added here when it's created, and `lint` flags
any page listed in **no** index — here, or in a subdirectory's own
`index.md`. Each entry's description is the linked page's frontmatter
`description`, so the index and the page can't drift. See
`docs/wiki-schema.md` for the page format and maintenance rules.
## Practice notes
- [The LLM-Wiki Pattern in gvt-dev](llm-wiki-pattern-in-gvt-dev.md) — How
Karpathy's LLM-maintained-wiki pattern maps onto gvt-dev surfaces that
predate maintain-wiki — docs/TOC.md, ADRs, run-retro/condense-lessons, and
audit-conventions' hygiene scanners.
- [`audit-conventions` as Proto-Lint](audit-conventions-as-proto-lint.md) —
How audit-conventions' hygiene scanners already act as an informal advisory
content-lint over docs/** and CLAUDE.md, and where the boundary with
maint
Details
- Kind
- OKF bundles
- Topic
- Productivity
- Publisher
- genvidtechnologies
- Origin
- okf_github
- Category
- dados
- Version
- 0.2
- Stars
- 1
- Last push
- 2026-09-01T15:19:57Z
- Repository state
- ativo
- Language
- JavaScript
- License
- MIT-0
- Added
- 2026-09-08 16:02:35
- Updated
- 2026-09-08 16:02:35
- Origin id
GenvidTechnologies/claude-code-plugin-gvt-dev:wiki/index.md
README
# claude-code-plugin-gvt-dev The **`gvt-dev` plugin** for Claude Code — shared skills, agents, and hooks used across Genvid game projects. The 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`). It is distributed through the [`claude-code-gvt-marketplace`](https://github.com/GenvidTechnologies/claude-code-gvt-marketplace) catalog (marketplace name `gvt-plugins`). ## Install ```text /plugin marketplace add https://github.com/GenvidTechnologies/claude-code-gvt-marketplace.git /plugin install gvt-dev@gvt-plugins ``` After installing, run the audit: ```text /gvt-dev:audit-conventions ``` The 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. For 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). ## What the plugin provides **Skills** (invoked as `/gvt-dev:<name>`): | Skill | Purpose | |-------|---------| | `commit-changes` | Create a git commit following the project's CLAUDE.md format | | `create-pr` | Open a PR (GitHub via `gh`, Bitbucket via copy-paste link) | | `plan-task` | Analysis → design → planning pipeline with user checkpoints | | `plan-next-issue` | Pick the next backlog issue and route it into `plan-task` (optionally triages first) | | `triage-issues` | Triage an issue backlog — dedup, enrich, link dependencies, split, stamp `triaged` | | `create-adr` | Add or chronologically insert an Architecture Decision Record | | `validate-changes` | Dispatch the validator agent on the project's full validation suite | | `rebase-branch` | Rebase a feature branch with conflict resolution guidance | | `rebase-stack` | Rebase a stacked branch after an earlier branch was squash-merged | | `split-branch` | Split a large branch into reviewable stacked branches | | `clear-worktree` | Tear down a git worktree safely, recovering unpushed work and worktree-keyed memory | | `run-retro` | Session retrospective — proposes doc / skill / agent improvements | | `sync-config` | Wraps `/plugin update gvt-dev` + audit re-run | | `cleanup-initiative` | Close out an initiative folder (optional convention) | | `condense-lessons` | Extract reusable insights from a lessons-learned doc | | `publish-npm-package` | Set up a package to publish on npmjs via OIDC trusted publishing | | `release-plugin` | Cut a plugin release — bump, tag, and bump the marketplace `source.ref` | | `release-npm-package` | Cut a routine npm package release — bump, tag, and trigger the OIDC publish workflow | | `reconcile-mcp-pin` | Reconcile agent tool inventories after a bundled MCP server pin bump / scope rename | | `migrate-cordova-ci` | Migrate a Cordova plugin's CI from CircleCI to GitHub Actions | | `audit-conventions` | Validate / migrate against the convention contract | | `maintain-wiki` | Maintain a project's LLM-wiki compounding-memory knowledge base (ingest / query / lint) | | `build-probe` | Build a throwaway probe to answer one checkable question, then promote or discard | **Agents** (dispatched via `subagent_type: "gvt-dev:<name>"`): `analyst`, `designer`, `planner`, `tech-writer`, `ts-implementer`, `validator`, `code-reviewer`, `issue-triage-analyst`, `wiki-librarian`. **Hook:** `pre-commit-lint` runs `commands.lint` from `.gvt-agent.json` before every `git commit` in the Bash tool. **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. ## The convention contract The plugin reads project context from four files in the consuming repo, in a contract documented at [`CONVENTIONS.md`](plugin/CONVENTIONS.md): | File | Purpose | |------|---------| | `CLAUDE.md` | Project context, imports `@CONVENTIONS.md` | | `CONVENTIONS.md` | Copy of the plugin's canonical contract, synced by `/gvt-dev:audit-conventions --fix` | | `docs/TOC.md` | Documentation index | | `.gvt-agent.json` | Capability registry — project name, commands, repo overrides, feature flags | Every 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. ## Migrating from the legacy template-rendered setup If your repo currently has a `burbank-claude-config` git submodule and a `claude-config.json` file at the root, run: ```text /gvt-dev:audit-conventions --fix ``` The 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. Review the plan, then run: ```text /gvt-dev:audit-conventions --fix --apply ``` The 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. ## Forking and adapting The 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. ## Contributing Development guide in [`CLAUDE.md`](CLAUDE.md). Highlights: - The plugin lives under `plugin/`; skills are directories with `SKILL.md`; agents are flat `.md` files in `plugin/agents/`. - Top-level frontmatter is fixed (`name`, `description`, plus the Anthropic-supported fields); custom expectations go under `metadata`. - Verb-noun skill names avoid collisions with built-in Claude Code skills. - Validate with `claude plugin validate plugin`. - Test `audit-conventions` with `node --test plugin/skills/audit-conventions/scripts/test/*.test.mjs`. - Commits in this repo use scope-based freeform messages — no ticket prefix.