Analyzer

What This Skill Does

The Analyzer skill acts as a senior technical analyst within your OpenClaw agent workflow. It performs deep, systematic scans of project repositories to extract critical insights regarding structure, architectural patterns, and conventions. Instead of simply listing files, it synthesizes information to provide a high-level project health assessment, flagging technical debt, identifying core UI/UX patterns, and creating a structured 'Handoff Contract' that ensures subsequent agents (like coders or designers) have the necessary context to perform tasks without redundancy. It is designed to act as the 'brain' of the development lifecycle, ensuring that all downstream work is informed by the existing reality of the codebase.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/cankocakulak/analyzer

Ensure that your agent has the necessary file system permissions to read the repository path you intend to analyze.

Use Cases

• Onboarding: Rapidly understand an legacy codebase when you join a new team or project.
• Feature Planning: Analyze existing modules to identify where to inject new logic before writing a single line of code.
• Technical Audits: Identify hotspots, complex dependencies, or patterns that contribute to technical debt.
• Refactoring Preparation: Determine the impact and reach of potential architectural changes by mapping current constraints.

Example Prompts

1. "@Analyzer, please map the project structure for /home/projects/e-commerce-api and focus specifically on the payment integration layer. I need to know the current error handling conventions."
2. "I'm onboarding onto this project. @Analyzer, run a full repository analysis and generate a health report with a focus on potential technical debt in the frontend."
3. "@Analyzer, analyze the authentication flow in the current codebase and provide a summary for the next agent to use when implementing OAuth2."

Tips & Limitations

• Be Specific: While the skill can perform a full repo analysis, providing a specific focus parameter yields more actionable, deep-dive results.
• Maintain Artifacts: The skill creates a docs/[project-name]/analysis.md artifact. Always check this file first before re-triggering an analysis to save processing time.
• Scope: The Analyzer does not write code or execute logic; it is strictly an observation and reporting tool. Do not expect it to fix the issues it uncovers. If your project is a single-file script, this skill is likely overkill.