shannon-analysis

Orchestrate software project analysis with sub-skills and 8D scoring.

2|Updated Sep 30, 2025

Search Tags:#analysis #complexity #Serena #8D

Ready to run

npx skills add https://github.com/krzemienski/shannon-framework --skill shannon-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shannon-analysis
Source: https://github.com/krzemienski/shannon-framework/tree/main/skills/shannon-analysis
Command: npx skills add https://github.com/krzemienski/shannon-framework --skill shannon-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires serena, sequential.

What problem does it solve?

Orchestrates Shannon's analysis workflows, invoking sub-skills with quantitative rigor and Serena context for thorough, artifact-driven results.

Core Features & Use Cases

Auto-detection of analysis type (codebase, architecture, debt, complexity)
Serena-backed historical context and progress tracking
Progressive invocation of sub-skills (project-indexing, confidence-check, etc.)
Quantitative outputs with MCP recommendations

Quick Start

Run a carbon-copy analysis that produces a structured report with 8D scoring and recommendations.

Frequently Asked Questions about shannon-analysis

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

FAQPage Schema

How do I perform quantitative analysis on a software codebase?▼

Quantitative analysis systematically measures code complexity, architecture patterns, and technical debt using automated discovery and scoring. Shannon-analysis orchestrates this by detecting your codebase structure, integrating historical context via Serena, and invoking specialized sub-skills to produce 8D-based quantification and structured reports.

Can I analyze technical debt and complexity across large enterprise repositories?▼

Yes. Shannon-analysis handles enterprise-scale codebases by applying Glob and Grep-based discovery to locate relevant code, automatically detecting whether your analysis targets debt inventories, architecture patterns, or complexity metrics, then invoking sub-skills progressively to enforce rigor across large repositories.

What's the difference between ad-hoc code inspection and systematic analysis?▼

Systematic analysis replaces manual inspection by automating discovery, context integration, and scoring. Shannon-analysis enforces this through structured workflows: it detects analysis type, applies Serena context for historical tracking, runs confidence checks, and produces quantified outputs with MCP recommendations instead of informal notes.

How does Serena context improve analysis accuracy?▼

Serena context integration provides historical project data and progress tracking, anchoring analysis results to prior findings and project state. Shannon-analysis uses this context to detect analysis type automatically, adjust scoring based on artifact history, and surface recommendations grounded in tracked complexity patterns.

Can shannon-analysis work with time-critical analysis requests?▼

Yes. Shannon-analysis handles time-critical inquiries by auto-detecting analysis scope—codebase, architecture, debt, or complexity—and invoking only necessary sub-skills. This efficiency, combined with structured output persistence and MCP recommendations, delivers rigorous results without ad-hoc delays.