ultrathink-detective

Name: ultrathink-detective
Availability: InStock
Author: MadAppGang

Audit codebases via AST commands to reveal architecture, implementation, and testing health issues.

278|29|Updated Nov 4, 2025

Search Tags:#AST #multi-perspective #holistic-analysis #debt #code-health

Ready to run

npx skills add https://github.com/MadAppGang/claude-code --skill ultrathink-detective-madappgang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ultrathink-detective
Source: https://github.com/MadAppGang/claude-code/tree/main/plugins/code-analysis/skills/ultrathink-detective
Command: npx skills add https://github.com/MadAppGang/claude-code --skill ultrathink-detective-madappgang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill combines all detective perspectives (architect+developer+tester+debugger) with an Opus model to perform holistic code health assessments.

Core Features & Use Cases

Multi-Dimensional Analysis: architecture, implementation, testing, debugging
Full AST Toolset: map, symbol, callers, callees, context, search
Comprehensive Report: integrated health and debt assessment

Quick Start

claudemem --nologo map "code health" --raw; claudemem --nologo context AppService --raw

Frequently Asked Questions about ultrathink-detective

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

FAQPage Schema

How do I audit code health across multiple systems using AST analysis?▼

AST-based multi-perspective audits examine architecture, implementation, and testing layers simultaneously. This Skill uses map, symbol, callers, and callees commands to reveal health issues, dependency patterns, and technical debt across complex codebases without grep or glob, producing architecture maps and exact impact locations.

Can I use AST analysis to trace root causes after incidents?▼

Yes. Multi-perspective AST analysis reconstructs full call chains, semantic relationships, and architectural context to identify root causes. It's designed for post-incident analysis, revealing how changes propagate through systems and exposing interconnected issues spanning multiple components.

What's the difference between AST audits and standard code reviews?▼

AST audits combine architect, developer, tester, and debugger perspectives in one holistic assessment, producing dependency tracing and call-chain evidence. Standard reviews typically cover single perspectives. This approach surfaces architectural debt, testing gaps, and implementation risks that isolated reviews miss.

Do I need special tools to run multi-perspective code health analysis?▼

Yes. This requires claudemem v0.3.0 in AST mode with access to map, symbol, callers, callees, context, and search commands. The environment must support semantic code analysis and dependency mapping without relying on grep or find operations.

When should I perform a comprehensive code health audit instead of a targeted review?▼

Use comprehensive audits for major refactors, security audits, architecture decisions, complex bugs spanning systems, and technical debt assessment. Targeted reviews work for isolated changes; holistic audits reveal interconnected health issues, testing gaps, and systemic risks that point reviews don't surface.

How do AST-based audits identify technical debt?▼

Multi-perspective analysis examines architecture (design violations), implementation (code complexity), and testing (coverage gaps) simultaneously using semantic symbol search and call-chain tracing. This reveals debt sources—poor abstractions, untested paths, tight coupling—and quantifies their health impact across the system.