skills

Release a Claude Code plugin distributed via git — bumps the version in its .claude-plugin/plugin.json, keeps any marketplace.json entry in sync, commits, and pushes. Use whenever the user says "release the plugin", "bump the plugin version", "publish the Claude Code plugin", "ship the plugin", "cut a plugin release", or otherwise wants to version a plugin whose plugin.json holds the version. NOT for tag-and-CI release flows where a pushed v* tag builds artifacts — use the `release` skill for those.

Release a new version of a project. Handles version bumping (alpha / release candidate / stable), tagging, pushing, creating a GitHub release with curated release notes, and monitoring the CI pipeline until success. Use whenever the user says "release", "new version", "tag a release", "bump version", "ship it", "cut a release", "cut an RC", "promote RC", or anything about creating a new project version/tag. NOT for releasing a Claude Code plugin that is versioned in its .claude-plugin/plugin.json and distributed straight over git with no tag-triggered build — use the `release-claude-code-plugin` skill for that.

Creates a "rule" — a short, always-on guidance file (Markdown with name/description frontmatter, optionally path-scoped) that is injected into an agent's context to enforce or nudge a standing behavior. Writes it either into this repo's rules/ library or a project's .claude/rules/ directory, walking from intent through a fit check, interactive follow-ups (path scope, enforce-vs-nudge, save location, duplicate check), and a terse draft. Use whenever the user wants to create, write, add, scaffold, or draft a rule / constraint / guardrail / coding convention / standing instruction / always-on guidance / .claude/rules entry, or turn a repeated correction ("stop doing X", "always do Y") into a permanent rule. NOT for: authoring a reusable multi-step procedure (use skill-creator); a delegatable subagent (use agent-creator); editing settings.json, hooks, or permissions (use update-config); or recording project-specific facts like build commands and directory layout (those belong in CLAUDE.md / AGENTS.md, not a rule)

Scan a repository and produce a comprehensive architectural blueprint document with tech stack, component maps, Mermaid diagrams, data flow, API surfaces, dependency graphs, and design patterns. Spawns parallel analysis agents for speed. Use whenever the user says "blueprint", "architecture overview", "architectural blueprint", "map this repo", "codebase analysis", "system design doc", "repo scan", "how is this repo structured", "document the architecture", or wants to understand, document, or map the architecture of a codebase. Also use when onboarding to a new codebase and wanting a high-level understanding, or when asked to create technical documentation for a project. For standalone C4 diagrams (context, container, component) without a full document, use the c4-diagrams skill instead.

Create C4 model architecture diagrams (system context, container, component, plus dynamic and deployment views) as Mermaid, for software systems and data platforms. Use when the user says "C4", "C4 model", "context diagram", "container diagram", "component diagram", "system context", "architecture diagram", "diagram this system", "visualize the architecture", "diagram the data platform / pipeline", or wants audience-appropriate views of a system at different zoom levels. Also use to review or fix an existing C4 diagram. For a full written blueprint document of a repository, use the blueprint skill instead.

Creates a Claude subagent definition file (a .md agent spawned via the Agent/Task tool) and iteratively improves it — the way skill-creator does for skills, but adapted to the physics of subagents (isolated context, return value is data not chat, tool allowlist as guardrail, name and description as delegation trigger). Walks you from intent through the design dimensions, writing the file, testing it on realistic delegation prompts, and tuning its trigger. Use whenever the user wants to create, design, write, scaffold, draft, or improve a subagent / sub-agent / custom agent / agent definition, build an agent for a skill's agents/ directory, set up a specialized agent to delegate to, or tune an existing agent's description / tools / model. NOT for: creating a skill (use skill-creator); orchestrating a multi-phase multi-agent build or "agent team" (use dev-team); writing a one-off Agent-tool prompt you will not reuse; or authoring a multi-agent Workflow script.

Record polished GIFs (and MP4/WebM/PNG) of terminal programs — CLIs, TUIs, REPLs, dotfiles, your own tools — by scripting them with VHS. Use this whenever the user wants to "make a gif", "record a terminal", "capture a CLI/TUI demo", "show this command running", "create a demo for the README", "animate my tool", "screen-record the terminal", or asks for an asciinema-style recording, a terminal screenshot, or a demo of how a command-line program behaves. Trigger even when the user only describes the behavior they want to capture (e.g. "show what happens when I run `mytool init`") without naming GIF or VHS explicitly.

Generate a hierarchical page index — a table-of-contents tree with per-section and per-block summaries — from a markdown or text document, using DSPy with ANY model (ollama, gemini, claude, openai, or anything litellm supports). Use this whenever the user wants to outline, index, map the structure of, build a TOC for, or extract the hierarchy of a document or markdown file, even if they don't say the words 'page index'. The script is self-contained and portable: it depends only on dspy, tiktoken, regex, and pydantic — no database, no server, no Memex install.

Orchestrate a multi-phase software development agent team with requirements gathering, planning, development, review, and reporting. Spawns specialized agents (requirements engineer, staff engineers, senior devs, QA, PO) that work in parallel workstreams with 95% certainty gates and quality reviews. Use whenever the user wants a full dev team, a coordinated multi-agent build, or says things like "build a team", "dev team", "agent team", "orchestrate development", or describes complex multi-phase work requiring planning, implementation, and review.

Close the loop on a PR that has been reviewed by an automated reviewer (Hermes Code Review, Gemini, CodeQL, Snyk, Dependabot, or any GitHub Actions bot that posts PR review comments with severity-tagged findings). Fetches the review, parses the findings, asks which ones to patch, generates the fixes, commits in logical chunks with conventional commit messages, pushes to the PR branch, and verifies the re-run CI. Use whenever the user says "address the PR review", "patch the findings", "respond to the Hermes/Gemini/CI review", "update PR X based on the review", "run the PR review cycle", or anything about triaging and applying an automated code-review bot's feedback. Also trigger this if the user opens a PR and the next step is clearly "now deal with the review comments".