claude

vornik-companion

Async-offload companion. Delegate reviews, audits, validations, research, summarization, and bulk RAG ingest to vornik-managed agents over MCP; results re-enter Claude's context via a SessionStart digest hook. Per-repo scoping (migration 75) so one project's RAG cleanly serves multiple repos. Also bundles operator lifecycle skills — configure-vornik, validate-install, troubleshoot-vornik, and report-problem — so your assistant drives Vornik's own tooling (config validate/reload, the published reference architecture, the doctor, the failure-class playbook, and the anonymized problem reporter) instead of improvising.

11 on GitHubby vornikv0.50.10Apache-2.0updated todaydevelopment
/

Plugin vornik-companion from marketplace vornik in EaseIT-cz/vornik. Commands read from the repo's manifest — today.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (8)

  • configure-vornik

    Teaches Claude how to help an operator configure a Vornik deployment — daemon settings, projects, swarms, workflows, models, secrets, channels. Use this skill whenever the user wants to set up, change, or add something to Vornik's configuration: "add a project", "change the model", "connect a channe

  • delegate

    Teaches Claude when to offload work to a vornik companion workflow rather than doing it inline. Use this skill when: (a) the user has the vornik-companion plugin installed (check by trying mcp__plugin_vornik-companion_vornik__catalog), (b) the task ahead is large, async-friendly, and doesn't need th

  • develop-with-memory

    Teaches Claude how to change code in a repository whose project memory is in Vornik, for ANY project: recall before reading code, design before changing it, keep memory current, and, where memory holds no design for the part being changed, write an as-built record of that part, have it reviewed, the

  • report-problem

    Teaches Claude how to help a user report a Vornik problem — a bug, a crash, a misbehaving swarm, or an INSTALL failure — as an anonymized GitHub issue on the public EaseIT-cz/vornik repo. Use this skill whenever the user says Vornik is broken / erroring / not installing / behaving wrong and wants to

  • troubleshoot-vornik

    Teaches Claude how to diagnose a Vornik deployment that is down, degraded, or failing tasks. Use this skill whenever the user says Vornik is broken, erroring, stuck, hanging, won't start, a task failed, a feature is dark, or a change didn't take effect. Vornik ships a rich diagnostic surface — a mul

  • validate-install

    Teaches Claude how to validate a Vornik deployment against the published reference architecture. Use this skill when the user asks whether an install is set up correctly, wants a post-install or post-upgrade check, asks for a health check / audit / review of a deployment, or reports that Vornik "isn

  • vornik-admin

    Use when the user wants you to set up or change their Vornik automations (projects, workflows, connections to mail, banking, calendar and other private services) through the Vornik admin tools. Vornik keeps every credential; the user approves each change on their phone.

  • vornik-docs

    Teaches Claude where Vornik's documentation lives, so it answers questions about Vornik from the docs rather than from guesswork. Use this skill whenever the user asks how a Vornik feature works, what a config key does, which flag a command takes, whether Vornik can do something, or asks for a doc l

Slash commands (20)

  • /vornik-companion:backlog-deposit

    File an off-scope finding into this repo's backlog, with dedup and a secret scan

  • /vornik-companion:delegate

    Delegate work to a vornik companion workflow asynchronously

  • /vornik-companion:memory-correct

    Refute a wrong/stale fact in vornik RAG (and optionally store the correction)

  • /vornik-companion:memory

    Show what Vornik's memory holds for this project, a page at a time, and how to forget or export it

  • /vornik-companion:peek

    List your outstanding vornik delegations

  • /vornik-companion:rag-ingest

    Bulk-ingest local files into vornik's project RAG memory via the companion-rag-ingest workflow, without burning client tokens on file content

  • /vornik-companion:recall

    Semantic-search this project's RAG memory via vornik

  • /vornik-companion:remember

    Deposit a note into this project's RAG memory via vornik

  • /vornik-companion:result

    Pull the final result of a completed vornik task into context

  • /vornik-companion:review

    Async architectural review of the current branch's diff

  • /vornik-companion:skill-approve

    Approve a draft vornik knowledge skill, promoting it to active (the human gate)

  • /vornik-companion:skill-get

    Fetch one vornik knowledge skill's full body

  • /vornik-companion:skill-list

    List vornik knowledge skills for review (by maturity)

  • /vornik-companion:skill-propose

    Propose a knowledge skill (instructional know-how) into vornik's skill store as a draft

  • /vornik-companion:skill-reject

    Reject or retire a vornik knowledge skill

  • /vornik-companion:skill-search

    Find active/trusted vornik knowledge skills relevant to the current work

  • /vornik-companion:skill-set-global

    Set (or clear) a vornik knowledge skill's GLOBAL reach — a global skill injects into every project's roles

  • /vornik-companion:status

    Check status of a specific vornik task

  • /vornik-companion:upload

    Upload local files as input artifacts + delegate ANY vornik workflow (RAG ingest, document architectural-review, data-validation, …) in one shot, without burning client tokens on file content

  • /vornik-companion:whoami

    Show which RAG project/scope this session is currently using

MCP servers (1)

  • vornik

    connects to: ${VORNIK_URL:-${user_config.vornik_url}}/api/v1/mcp/companion

Hooks (7)

  • SessionStart

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh"

  • SessionStart

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh" --refresh

  • PreToolUse

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/recall-nudge.sh" observe

  • PostToolUse

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/recall-nudge.sh" recalled

  • PostToolUse

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/hints.sh" call

  • PostToolUseFailure

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/hints.sh" failed

  • UserPromptSubmit

    bash "${CLAUDE_PLUGIN_ROOT}/hooks/hints.sh" prompt

View source on GitHub vornik.io

More from EaseIT-cz/vornik

All 2 plugins →

0.45.8: the recall hint after a failed test run names the exact recall tool and says to call it now, the wording that was followed in every measured Claude Code run (the advisory text was followed in none). 0.45.7: the hint hooks' git-options group is disjoint (a -C or -c value cannot start with a dash), the rule the Hermes plugin now uses; bash's regex was already fast, so this is for parity. 0.45.6: the hint hooks match a git commit after variable assignments with disjoint value pieces, the rule the Hermes plugin now uses (its old rule backtracked exponentially; grep -E never did). 0.45.5: the hint and recall-nudge hooks claim their state with an exclusive file create (bash noclobber, O_EXCL) instead of mkdir, which uutils coreutils on Ubuntu 26.04 does not make exclusive, so a hint fires once, a session's outcomes upload once, and each read takes its own nudge slot (GitHub #687). 0.45.4: the User-Agent hints.sh sends names 0.45.4; the shared hint script is unchanged otherwise, and hooks/hints_cases.json in the Claude Code bundle now holds the hint rules to the same cases as the Hermes plugin's Python port (GitHub #686). 0.45.3: the design-edit hint matches a design document whatever the case of its name, so https://docs.vornik.io counts (GitHub #682). 0.45.2: the recall nudge keeps its state only in the plugin's data directory, or in the per-user runtime directory when the user owns it, never in a shared temp path, and refuses a state directory that is a symlink or that another user owns (GitHub #651). 0.45.1: the design-edit hint also sees a design document written through a shell command (a heredoc, a redirection, tee, sed -i, cp or mv), read from the command text and never run (GitHub #653). 0.45.0: just-in-time hints (GitHub #634). hooks/hints.sh, shared with the Claude Code bundle, prints a short hint from the project's catalogue when it applies: after a commit (send the diff for review), after a design document is patched (ingest it), after a test run whose

10 skills · 1 MCP server · hooks

11

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.

5 commands

HKUDS/CLI-Anything 58,665

Automates browser interactions for web testing, form filling, screenshots, and data extraction

12 skills

vercel-labs/agent-browser 50,373

Use Alibaba Open Code Review from local Codex.

2 skills

alibaba/open-code-review 50,068

Maintain vornik-companion?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins2 plugins