agw-deep-code-analysis

Analyze codebases to document architecture, behavioral patterns, and project conventions.

2|1|Updated Feb 17, 2026

Search Tags:#workflow #architecture #code analysis #documentation #refactoring

Ready to run

npx skills add https://github.com/cucurb-it/analysis-gated-workflow-skills --skill agw-deep-code-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agw-deep-code-analysis
Source: https://github.com/cucurb-it/analysis-gated-workflow-skills/tree/main/skills/02-deep-code-analysis
Command: npx skills add https://github.com/cucurb-it/analysis-gated-workflow-skills --skill agw-deep-code-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of superficial code reviews by enforcing a rigorous, evidence-based analysis of existing codebases, ensuring that architectural decisions are grounded in observed reality rather than assumptions.

Core Features & Use Cases

Systematic Code Analysis: Provides a structured framework to analyze architecture, behavioral execution paths, data models, and performance characteristics.
Project Convention Enforcement: Automatically scans and extracts critical rules from project-specific documentation like .claude and .github folders to ensure compliance.
Use Case: Use this skill when you need to perform a deep-dive investigation into a complex module or legacy component before planning any refactoring or feature implementation.

Quick Start

Initiate the deep code analysis process by reading the skill instructions and applying them to the target component in your current session.

Frequently Asked Questions about agw-deep-code-analysis

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

FAQPage Schema

How do I analyze codebase architecture before planning a refactoring?▼

To analyze codebase architecture before refactoring, you need an evidence-based approach that documents behavioral execution paths, data models, and dependencies rather than relying on assumptions. This ensures architectural decisions are grounded in observed component reality.

When do I need deep code analysis for a legacy component?▼

You need deep code analysis for a legacy component when you require a rigorous understanding of system dependencies and performance characteristics before implementation. It provides a structured framework to document architecture and extract project conventions from existing documentation.

Can I enforce project-specific coding conventions during code analysis?▼

Yes, you can enforce project-specific coding conventions during code analysis by automatically scanning and extracting critical rules from documentation folders. This ensures compliance with established project-level coding standards throughout the architectural investigation.

What's the best way to document software architecture using evidence-based analysis?▼

The best way to document software architecture using evidence-based analysis is applying a systematic framework that evaluates behavioral patterns and performance characteristics. This grounds architectural decisions in observed reality and satisfies traceable documentation requirements for complex modules.

Does deep code analysis work with existing project documentation?▼

Yes, deep code analysis works with existing project documentation by automatically scanning project-specific folders to extract critical rules. It integrates these conventions into the comprehensive architectural review to ensure adherence to established standards.