Scaffold a reference HTTP control-channel gateway (sample shell clients + bun TUI) into /control/, OR print the control-channel protocol docs. Reference example based on the dirty-claude project (Phase 1 patched binary exposes HTTP+SSE server on 127.0.0.1:$DCPORT inside the running Claude). NOT a generic abstraction …
Extract Claude Code's cli.js + native .node modules from an installed claude binary (or a binary you pass as positional arg). Output lands in dist/ /. Required before aio-patch-compile. Default arch detected from host; ARCH env var overrides for cross-arch extraction.
Exec the compiled patched Claude binary at dist/ /claude. Pass-through args + env. Requires aio-patch-compile to have been run first (sentinel: dist/ /claude exists).
Scaffold a new Claude-binary-patching project at CWD (or [targetdir]). Copies generic pipeline tools (extract/build/run, Python pipeline scripts, cli-nav AST navigator) + generic docs/guides into the target. Patches.json starts EMPTY — user fills it in; a reference example from the dirty-claude project is shipped…
Runs an adaptive, project-aware code-review workflow and carries Google's engineering code-review playbook it applies. The workflow profiles the project, detects its real lint/type-check/test tooling and house conventions, reviews on two tracks (mechanical + semantic 8-dimension rubric), adversarially verifies each…
Runs an adaptive, project-aware code-review workflow (profile the project, detect its lint tools + conventions, run mechanical + semantic review, consolidate into an LGTM verdict) and carries the Google eng-practices playbook it applies — reviewer (what to look for, when to approve, severity-labeled comments, handling…
Find code, locate implementations, and understand how features work via parallel Explore agents. Step 1 of the codeflow discover → map → plan trio used before implementation.
Generate comprehensive architecture documentation — the Codebase Oracle that writes docs, module docs, and dependency maps — powered by the GitNexus knowledge graph and LSP analysis.
Install, configure, and manage the GitNexus code intelligence engine — index codebase, setup MCP, check status, troubleshoot, and document local git-hook auto-refresh for master-only workflows.
Trace dependencies, call graphs, and blast radius for a file/function/module via GitNexus + LSP. Step 2 of the codeflow discover → map → plan trio (after aio-discover, before aio-plan).
Synthesize discovery and dependency mapping into a step-by-step implementation plan via planner agent. Step 3 of the codeflow discover → map → plan trio (after aio-discover and aio-map).
Deep multi-agent code review — dispatch a fleet of parallel specialized agents (security, architecture, quality, performance) with GitNexus domain analysis. Use before merging a PR or after a major feature lands when a single-pass review is too shallow. For a quick pre-commit sanity check use aio-review-quick.
Quick pre-commit sanity check — validate post-implementation changes against the aio-snapshot baseline via change detection, duplication detection, and type checking. Light pass; for deep multi-agent review use aio-review-deep.
Rubber duck companion — Claude plays the duck (asks questions, probes assumptions, never rushes a solution); the user explains the problem step by step to externalize reasoning.
Web UI design and review advisor — applies UX psychology, interaction patterns, WCAG accessibility, and modern CSS to design new interfaces or critique existing ones. Use proactively when reviewing any frontend UI, scaffolding new components, or deciding layout/color/typography trade-offs.
Read and manage GitHub repos, pull requests, issues, releases, and branches via github-mcp (auto-installs if missing). Use when the user mentions a GitHub URL, asks to open/review/merge a PR, comment on an issue, list repos, trigger a release, or run any GitHub action programmatically.