CLI Actions
When you run npx zenoai, Zeno scans the project and prompts you to choose one of four actions. Each action is built around a specific review question.
Tell me if this is safe to ship
A read-only, project-aware ship-readiness report. Zeno detects the project type, identifies the product’s critical user flow, and checks whether repository evidence appears to connect that flow to a real outcome.
Use this after an agent makes changes, before a significant merge, or anytime you want a current read on the codebase.
Output includes:
- Project type and detection confidence
- Private preview, public launch, and paid traffic readiness
- Hard blockers, soft blockers, and code ownership risks
- Severity and certainty for every finding
- Repository evidence and runtime-verification requirements
- Safest next step before shipping
Check for security risks
A local static scan for obvious security signals. Zeno looks for patterns that commonly indicate security exposure: hardcoded secrets, missing environment validation, exposed API routes, insecure data writes, and similar signals.
This does not replace a full security audit, but it surfaces the most common AI-agent mistakes quickly. No API key is required — this runs entirely on your machine.
Make this code easier to work with
A guarded cleanup flow for files Zeno determines are safe to touch. Zeno avoids broad, sweeping changes. It looks for the smallest safe improvement — typically extracting pure helpers, removing duplication, or improving naming in low-risk areas.
Before any file is considered for cleanup, Zeno filters out generated files, config files, framework boilerplate, and high-consequence untested code — these are skipped before any model call, not after a failed attempt.
Zeno will skip files where a cleanup would be mostly cosmetic or carry meaningful risk without clear value.
Split large files
A deterministic split for files containing static constants or data that have grown too large. Zeno splits only what is clearly separable — exported constants, type definitions, static configuration — and does not restructure logic. No API key is required for this step.
Reports from a ship-readiness run
Zeno saves the complete report locally in three formats:
- JSON for structured processing
- HTML for reading and printing
- CSV for filtering and sharing findings
The HTML report includes a Print / Save as PDF action. PDF creation is handled by the browser’s print dialog; Zeno does not generate a PDF file directly.