Maleick

Delegate GitHub issue-to-PR orchestration to the AutoShip OpenCode plugin.

Implementer role — writes code to implement features or fixes

AutoShip orchestration for OpenCode-only workers

Display current AutoShip orchestration status — running agents, quota bars, progress, token usage

Interactive setup wizard for AutoShip on OpenCode — model selection, tool detection, concurrency tuning

Post-completion verification pipeline for OpenCode — review, simplify, re-verify, PR creation, CI monitoring, cleanup

Lead role — coordinates multiple agents and manages orchestration flow

Planner role — analyzes issues and creates implementation strategies

Use when a codebase has accumulated technical debt including dead code, legacy fallbacks, circular dependencies, duplicate types, weak typing, defensive programming slop, or error handling anti-patterns that need systematic excavation and cataloging before restoration.

Use when a codebase has accumulated technical debt including dead code, legacy fallbacks, circular dependencies, duplicate types, weak typing, defensive programming slop, or error handling anti-patterns that need systematic excavation and cataloging before restoration.

Use when a repository needs systematic technical-debt excavation in Codex, including dead code, legacy fallbacks, circular dependencies, duplicate types, weak typing, DRY issues, or error-handling cleanup.

Run a subagent-first structured improve-verify loop in OpenCode. Activate with /autoresearch or specialized modes like /autoresearch:plan, /autoresearch:debug, /autoresearch:fix, /autoresearch:learn, /autoresearch:predict, /autoresearch:scenario, /autoresearch:security, /autoresearch:ship. Supports recursive self-improvement loops.

Use when working against a local GhidraMCP GUI or headless server, especially for binary import, metadata verification, analysis, export checks, or raw endpoint access.