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 ship-readiness report. Zeno scans your project, identifies high-risk areas, missing verification, and untested paths, and tells you whether the codebase is ready to ship.

Use this after an agent makes changes to a feature branch, or before any significant merge.

Output includes:

• Overall ship-readiness verdict
• Blocking issues with risk severity
• Missing verification gaps
• Safest next step before shipping
• Do-not-touch zones

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.

Make this code easier to work with

A guarded cleanup flow for files Zeno determines are safe to touch. Zeno will not run broad rewrites. It identifies the smallest safe improvement — typically extracting pure helpers, removing duplication, or improving naming in low-risk areas.

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.