shuv-pi

Ask the user structured questions (single choice, multi-select, or free text) using the ask_questions tool. Use this when you need clear, normalized answers.

Unified browser automation skill. Single entry point for Rodney CLI, agent-browser CLI, dev-browser (TypeScript/Playwright), and browser-tools helper scripts.

Query up-to-date library documentation and code examples using the Context7 MCP server. Requires CONTEXT7_API_KEY.

Web search, code context, company research, and deep research via Exa API. Use when searching the web, finding code examples/docs, researching companies, crawling URLs, or running deep AI research tasks. Triggers on: web search, find code, research company, crawl page, people search.

Methodical investigation and root-cause analysis of bugs and issues before proposing solutions. Use when asked to investigate a bug, diagnose an issue, find the root cause of a problem, debug unexpected behavior, trace an error, or figure out why something is broken. Enforces hypothesis-driven debugging and avoids premature fixes.

Quick patch version bump workflow — run tests, bump version in package.json and all version references, commit, push, relink binaries, and verify. Use when asked to bump the version, do a patch release, increment the version number, cut a patch, or publish a new version.

Create well-structured atomic git commits from uncommitted changes using conventional commit messages. Use when asked to commit, stage, create commits, clean up uncommitted work, or prepare changes for push. Handles grouping related changes into logical commits and writing proper commit messages.

Deep-dive codebase exploration producing a TL;DR summary and detailed architectural analysis. Use when asked to explore a codebase, understand a project structure, analyze architecture, explain how a codebase works, map out a repository, or answer "what does this project do". Covers technology stack, core workflows, data flow, and key components with file references.

Execute implementation tasks from a plan document (PLAN-*.md), working through checkbox items sequentially. Use when asked to implement a plan, execute a plan, work through plan tasks, start implementation from a plan file, or carry out planned changes. Tracks progress by checking off completed tasks in the plan file.

Create well-structured GitHub issues using the gh CLI with research-enriched context. Use when asked to create a GitHub issue, file a bug report, open a feature request, report a problem, or document a task as an issue. Researches similar implementations, adds acceptance criteria, and includes code references.

Fetch and merge a GitHub PR locally for testing without pushing or closing the PR. Use when asked to locally merge a PR, test-merge a pull request, checkout and merge a PR for local testing, or pull a PR into a local branch. Accepts PR URLs, numbers (#14, 14), or gh references. Does NOT push to GitHub or close PRs.

Critically review technical plan documents (PLAN-*.md) against the current codebase before implementation. Use when asked to review a plan, validate a plan, check a plan for issues, audit an implementation plan, or assess whether a plan is ready to implement. Catches design flaws, codebase mismatches, and risky assumptions.

Transform conversation context into an actionable plan document (PLAN-*.md) with task breakdowns, code references, and implementation order. Use when asked to create a plan, write a plan document, turn a discussion into actionable steps, plan out a feature, create a task breakdown, or draft an implementation roadmap. Does NOT implement — only writes the plan.

Drive Zellij terminal multiplexer sessions for testing terminal applications and workflows. Use for running commands in multiple panes, capturing output, simulating user input, and orchestrating complex terminal test scenarios.