analyze

Orchestrate codebase analysis workflows via brain-hooks with step-based JSON communication.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/loriensleafs/brain --skill analyze-loriensleafs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/loriensleafs/brain/tree/main/apps/claude-plugin/skills/analyze
Command: npx skills add https://github.com/loriensleafs/brain --skill analyze-loriensleafs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill orchestrates immediate codebase analysis workflows by invoking brain-hooks for analysis requests, ensuring an immediate, guided workflow without manual exploration.

Core Features & Use Cases

  • IMMEDIATELY trigger analysis workflows via brain-hooks when users request codebase analysis, architecture reviews, security assessments, or quality evaluations.
  • Manage step-based JSON communication and state persistence to /tmp, following the defined workflow with steps (EXPLORATION, FOCUS SELECTION, INVESTIGATION, SYNTHESIS).
  • Support end-to-end analysis in large repositories by delegating tasks to the appropriate brain-hooks plugins and tracking findings, questions, and priorities.

Quick Start

Use the brain-hooks analyze command to start the workflow: echo '{"stepNumber": 1, "totalSteps": 6, "thoughts": "Starting analysis"}' | ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/brain-hooks analyze

Frequently Asked Questions about analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate codebase analysis for architecture and security reviews?

Automated codebase analysis is orchestrated by triggering analysis workflows via brain-hooks, which guide end-to-end architecture and security assessments across repositories without manual exploration.

What is the workflow for conducting a repository security assessment?

A repository security assessment follows a structured workflow with defined steps: EXPLORATION, FOCUS SELECTION, INVESTIGATION, and SYNTHESIS, managing state persistence and step-based JSON communication throughout the process.

Can I use this analysis workflow to evaluate code quality in large repositories?

Yes, you can evaluate code quality in large repositories by delegating analysis tasks to appropriate brain-hooks plugins, which track findings, questions, and priorities across the entire codebase.

How do I start a codebase analysis workflow using brain-hooks?

Start a codebase analysis workflow by invoking the brain-hooks analyze command with a JSON payload containing stepNumber, totalSteps, and thoughts, passing it through the brain-hooks script to initialize the process.

Does codebase analysis require any external dependencies or plugins?

No external dependencies are required, but the analysis workflow relies on brain-hooks plugins to delegate tasks and manage step-based JSON communication, persisting state to the /tmp directory during execution.

What are the limitations of orchestrating codebase analysis workflows?

Limitations include reliance on /tmp for state persistence and a fixed six-step progression, meaning workflows are bound to the defined EXPLORATION through SYNTHESIS phases without custom step configuration.