analyze-codebase
Analyze Codebase
Run the Skene CLI to analyze the codebase. The CLI does the analysis, not you.
Critical rule
Do NOT substitute your own PLG analysis, findings, or guesses if the CLI fails. Run the CLI, present its output on success, report the error on failure. That's it.
Agent behavior rules
- Autonomous. Run the CLI, present results, suggest next step. No mid-flow questions.
- User cannot type into agent terminals. The agent handles all CLI input. Pipe safe defaults for routine prompts. Kill stuck terminals and re-run with piped input.
Steps
-
Discover CLI options Run
uvx skene analyze --helpto see available flags. Use only flags that appear in the output. -
Verify configuration
More from skenetechnologies/skene
deploy-telemetry
Set up analytics and tracking infrastructure for growth loops. Use when the user says "deploy telemetry", "set up analytics", "tracking", "events", "push to supabase", or "skene push".
2validate-loop
Check if growth loop requirements are actually implemented in the codebase. Use when the user says "validate", "check status", "skene status", "is it done", or "verify implementation".
2plan-growth-loop
Generate prioritized growth loops with implementation roadmaps based on codebase analysis. Use when the user says "plan", "growth loops", "prioritize", "what should I build", or "roadmap".
2build-implementation
Generate context-aware implementation prompts for a selected growth loop. Use when the user says "build", "implement", "generate code", "create prompt", or "how do I build this".
2initialize-config
Set up Skene configuration for a project. Use when starting a new PLG analysis, when .skene.config is missing, or when the user says "skene init", "set up skene", or "configure skene".
2