analyze

Investigate codebases and workflows to identify causes, risks, and improvements.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/ssccio/cc-on-web-base --skill analyze-ssccio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/ssccio/cc-on-web-base/tree/main/skills/analyze
Command: npx skills add https://github.com/ssccio/cc-on-web-base --skill analyze-ssccio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn messy, incomplete, or complex situations—like bugs, performance issues, or security concerns—into clear findings and prioritized next steps based on evidence.

Core Features & Use Cases

  • Systematic context gathering: reviews relevant files and related history to ground the analysis in real information.
  • Structured investigation: identifies patterns, antipatterns, execution flow, dependencies, and edge cases without jumping to conclusions.
  • Debugging-ready output: uses a 4-phase protocol for bug analysis to prioritize root cause, compare working vs broken deltas, and apply a 3-failure circuit breaker when hypotheses stall.
  • Actionable synthesis: produces objectively grounded summaries, key findings, and recommendations prioritized by impact, including risks and tradeoffs for architecture.

Quick Start

Ask the AI to run deep analysis on the problem, explicitly requesting file-and-line citations and a prioritized recommendation plan.

Frequently Asked Questions about analyze

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

FAQPage Schema
How do I find the root cause of a bug in my codebase?

To find the root cause of a bug, you need systematic context gathering and structured reasoning. This approach uses a 4-phase protocol to compare working versus broken deltas and applies a 3-failure circuit breaker when hypotheses stall.

What is the best way to identify performance bottlenecks in operational workflows?

Identifying performance bottlenecks requires thorough, evidence-based investigations of operational workflows. This process reviews relevant files and execution flow to ground the analysis in real information and produce prioritized recommendations.

How does an evidence-based security review work for codebases?

An evidence-based security review works by systematically gathering context and identifying patterns, antipatterns, and edge cases across codebases. It avoids jumping to conclusions and outputs objectively grounded summaries with prioritized risk findings.

Can I use deep analysis for architecture evaluation and tradeoff assessment?

Yes, you can use deep analysis for architecture evaluation. It identifies dependencies and improvement opportunities, producing an objective synthesis that includes risks and tradeoffs for architecture prioritized by impact.

How do I get actionable fixes with file-and-line citations during debugging?

To get actionable fixes with citations, request a deep analysis on the problem. The output provides objectively grounded summaries, key findings, and a prioritized recommendation plan explicitly citing relevant file and line evidence.

What should I do when my debugging hypotheses stall and I cannot find the root cause?

When debugging hypotheses stall, apply a 3-failure circuit breaker. This structured investigation protocol prevents looping by forcing a re-evaluation of context and shifting the analysis away from unproductive root cause guesses.