travisennis

Run fallow static analysis to find dead code, duplication, complexity issues, and architecture drift. Use before committing, after generating code, or when asked to clean up the codebase.

How to build and drive acai end-to-end to verify changes at its real surface.

Run a focused review-readiness pass on a nearly finished change before commit. Scales the review to change size (XS/S = one pass, M = two passes, L/XL = three sequential passes covering rules conformance, correctness/source-of-truth, and overengineering). Then synthesize and apply the worthwhile fixes.

Analyzes the current session to identify self-improvement opportunities for acai.

Debugging tools and techniques for acai. Use when investigating errors, analyzing session behavior, or troubleshooting issues in the acai CLI application. Includes guidance on reading logs, session files, and common error patterns.

Manually test acai features by running the app in tmux, interacting with the REPL, and inspecting logs and session files. Use after implementing a feature to verify it works end-to-end.

Go through Open, Pending, and Blocked tasks in the backlog and make sure all decisions are made, dependencies are correct, and no open questions remain. The goal is to get tasks into a ready state for work.

REQUIRED when adding OpenCode Zen models - provides a script that fetches accurate context, max tokens, pricing, and capabilities from the API. Use this skill whenever the user asks to add, register, or configure a new OpenCode Zen model. Do NOT guess model specifications—always fetch real data from the API.

REQUIRED when adding OpenRouter models - provides a script that fetches accurate context, max tokens, pricing, and capabilities from the API. Use this skill whenever the user asks to add, register, or configure a new OpenRouter model. Do NOT guess model specifications—always fetch real data from the API.

Survey a codebase as a senior advisor, find the highest-value improvement opportunities, present them for acceptance, and create ahm tasks for accepted findings. Strictly read-only on source code — never implements, fixes, or refactors anything itself.