vvkit

Plugin vvkit from marketplace vv-agent-kit in vadimvitvickiy/vv-agent-kit. Commands read from the repo's manifest — 16 days ago.

Skills (19)

• capturing-decisions

  Use when a decision, correction, or design rationale emerges that would otherwise be lost when the session ends.

• choosing-subagent-models

  Use when about to launch any subagent — a research or exploration agent, a reviewer, an implementer, a parallel fan-out, or a fork.

• committing-changes

  Use when writing a commit message, opening a pull request, titling and describing a change for someone else to review, or deciding how to integrate a finished branch.

• debugging-systematically

  Use when a test fails, a bug is reported, or observed behavior does not match expectation, and before proposing or applying any fix.

• delegating-work

  Use when a change is expected to span multiple files or modules, or when deciding whether to hand work to subagents, run them in parallel, or keep it in the main conversation.

• designing-changes

  Use when asked to build, add or change behavior and the approach has not been agreed yet, when a request is open-ended or ambiguous about scope, or when an idea needs shaping into a design before any code is written.

• exploring-a-codebase

  Use when starting work in an unfamiliar repository, when locating code across many files, or when a project's code map or architecture notes look stale.

• injecting-dependencies

  Use when writing a constructor or initialiser, when a type needs a collaborator to do its work, or when adding a parameter so something can be swapped in a test.

• planning-changes

  Use when an agreed design needs turning into an implementation plan, when a written plan is about to be carried out, or when resuming a plan part-way through after a break or a compaction.

• pruning-tests

  Use when auditing a test suite for low-value tests, or when deleting, merging or rewriting existing tests or test doubles.

• reflecting-on-changes

  Use when code has just been written or modified and the work is about to be reported as done — the self-review pass over your own unstaged changes.

• resolving-conflicts

  Use when a merge, rebase or cherry-pick stops on a conflict, or when integrating a branch across a rename, move or other refactor made on the other side.

• reviewing-code

  Use when reading a diff or pull request for defects, when acting as the reviewer on a change you did not write, or when review feedback arrives on your own change.

• verifying-changes

  Use when deciding what to build, run, or test after a change, and before claiming that work is complete, fixed, or passing.

• writing-comments

  Use when writing or reviewing comments and doc comments, or when a diff adds explanatory prose alongside code.

• writing-logs

  Use when adding or reviewing log statements, or when deciding what level a message belongs at.

• writing-project-instructions

  Use when creating or editing a CLAUDE.md or AGENTS.md, when it has grown long, or when a rule in it also exists in an installed skill.

• writing-skills

  Use when authoring or editing a skill, agent, command or hook for this kit, or when deciding whether a piece of guidance belongs in a skill at all.

• writing-tests

  Use when adding or changing behavior, fixing a bug, or judging whether an existing or generated test earns its place.

Slash commands (9)

• /vvkit:explore

  Refresh the generated code map and reconcile the hand-written architecture constraints against the code.

• /vvkit:merge

  Commit staged work, merge the base into a finished branch, verify, merge the branch into the base, and remove the branch and its worktree.

• /vvkit:onboard

  Scaffold the kit's .claude/ and .agents/ layout into a project, verifying every asserted convention against the code first.

• /vvkit:open-pr

  Write a pull request title and description for the current branch, push it, and open the creation page in the browser.

• /vvkit:rebase

  Rebase the current branch onto a local or remote base, adapting it to refactors the base made.

• /vvkit:review

  Review the local diff or a branch against the kit's standards, delegating to the reviewer agent for the detected language.

• /vvkit:scripts

  Generate this project's build, test and lint scripts, verified by running them.

• /vvkit:wire

  Reconcile a CLAUDE.md against the skills this plugin actually installs, replacing duplicated rules with references.

• /vvkit:worktree

  Hand one or more independent tasks to agents that each work in their own git worktree and branch.

Subagents (3)

• architecture-surveyor

  Maps the architecture around a planned change — sibling features, the types crossing each boundary and who owns them, how each abstraction was extended before — with counts and file:line. Use whenever a change is being designed or planned, in the background alongside the caller's own reading.

• commit-reviewer

  Reviews commits that already exist for defects. Use after a series of commits lands, or when asked to review the last few commits or a commit range.

• test-runner

  Runs a known test, build or lint command and reports its exit code, counts and failures verbatim. Use when the command is already known and its output should stay out of the main conversation.

Hooks (4)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/session-context.sh"

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}/hooks/using-vvkit.sh"

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}/hooks/subagent-model-gate.sh"

• Stop

  "${CLAUDE_PLUGIN_ROOT}/hooks/test-gate.sh"

Similar plugins