Best use case
analyze is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Deep analysis and investigation
Teams using analyze should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/analyze-neversight/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How analyze Compares
| Feature / Agent | analyze | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Deep analysis and investigation
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Deep Analysis Mode
[ANALYSIS MODE ACTIVATED]
## Objective
Conduct thorough analysis of the specified target (code, architecture, issue, bug, performance bottleneck, security concern).
## Approach
1. **Gather Context**
- Read relevant files
- Check git history if relevant
- Review related issues/PRs if applicable
2. **Analyze Systematically**
- Identify patterns and antipatterns
- Trace execution flows
- Map dependencies and relationships
- Check for edge cases
**For Debugging/Bug Analysis (4-Phase Protocol)**
When analyzing bugs or issues, follow systematic debugging:
- **Root Cause First** - Never skip to fixes
- Read ALL error messages
- Reproduce consistently
- Document hypothesis before looking at code
- **Pattern Analysis** - Find working vs broken
- Compare with working similar code
- Identify the specific delta
- **3-Failure Circuit Breaker** - If stuck:
- After 3 failed hypotheses, question the architecture
- The bug may be elsewhere entirely
3. **Synthesize Findings**
- Root cause (for bugs)
- Design decisions and tradeoffs (for architecture)
- Bottlenecks and hotspots (for performance)
- Vulnerabilities and risks (for security)
4. **Provide Recommendations**
- Concrete, actionable next steps
- Prioritized by impact
- Consider maintainability and technical debt
## Output Format
Present findings clearly:
- **Summary** (2-3 sentences)
- **Key Findings** (bulleted list)
- **Analysis** (detailed explanation)
- **Recommendations** (prioritized)
Stay objective. Cite file paths and line numbers. No speculation without evidence.Related Skills
analyze-rust-optimizations
This skill performs thorough analysis of Rust libraries to find optimization opportunities. It should be used when reviewing Rust code for performance improvements, memory efficiency, or when profiling indicates bottlenecks. Focuses on runtime performance and memory usage through dynamic profiling tools and static code analysis.
analyze-project-architecture
LLM-based architectural analysis that transforms raw project data into meaningful structure
analyze-pr-performance
Analyze code review pipeline performance for a specific PR. Use when investigating slow PRs, identifying bottlenecks, or debugging performance issues in code reviews.
analyze-m1-module-for-migration
Systematically analyze a Magento 1 module to determine its purpose, usage, and migration requirements for Magento 2. Use when you need to decide whether to migrate a M1 module, find alternatives, or skip it.
analyze-function
Deep line-by-line analysis of a function or method. Explains what each line does, why it's written that way, performance implications, edge cases, and design patterns. Use when user says "analyze-function", "analyze {function}", "deep dive on {function}", or "explain {function} line by line".
analyze-friction
Orchestrate 3-stage friction analysis workflow across conversations. Extracts raw friction, abstracts patterns, and presents for approval. Use when user wants to analyze conversation history for improvement opportunities.
analyze-codebase
Analyze a codebase to generate a comprehensive architecture and structure report. Use when user wants to understand a codebase, explore project structure, or generate analysis.
analyze-code
Deep code analysis using consultant agent. Identifies technical debt, risks, and improvement opportunities.
analyze-code-structure
Examine code organization and identify structural patterns. Use when reviewing module design.
analyze-architecture
Comprehensive brownfield architecture analysis for existing codebases. Discovers structure, identifies patterns, assesses quality, calculates production readiness, and provides actionable recommendations. Use when analyzing existing codebases to understand architecture, assess quality, or prepare for modernization.
acc-analyze-solid-violations
Analyzes PHP codebase for SOLID principle violations. Detects God classes (SRP), type switches (OCP), broken contracts (LSP), fat interfaces (ISP), and concrete dependencies (DIP). Generates actionable reports with severity levels and remediation recommendations.
30-analyze-impact-150
[30] ANALYZE. Understand how changes impact the system — what's the core, what's affected, what depends on what. Use when planning changes, analyzing systems, debugging issues, or anytime you need to see the full picture of cause and effect. Triggers on "what's affected", "impact analysis", "dependencies", "scope mapping", or when you need to understand ripple effects.