dissect

Evaluate codebases for reliability and maintainability risks with structured findings.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/li3p/skills --skill dissect-li3p
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dissect
Source: https://github.com/li3p/skills/tree/main/skills/dissect
Command: npx skills add https://github.com/li3p/skills --skill dissect-li3p

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performs a deep structural review of a file, module, or directory to surface reliability, edge-case handling, and maintainability issues.

Core Features & Use Cases

  • Comprehensive evaluation across error handling, edge cases, state and concurrency, API contracts, dependencies, and code structure.
  • Actionable findings with precise severity, file location, problem description, and recommended fixes.
  • Useful for focused code reviews, architectural audits, and ongoing maintainability improvements.

Quick Start

Review the target codebase to surface reliability and maintainability concerns.

Frequently Asked Questions about dissect

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

FAQPage Schema
How do I review a codebase for reliability and maintainability risks?

To review a codebase for reliability and maintainability risks, apply a structural evaluation to single files, modules, or entire repositories to surface issues across error handling, edge cases, and state management.

What does a structural code review cover for concurrency and edge cases?

A structural code review covers concurrency, edge cases, state, API contracts, and dependencies. It evaluates code structure to surface maintainability issues and returns findings with severity, location, problem, and concrete fixes.

Can I audit a single file for error handling and API contract issues?

Yes, you can audit a single file for error handling and API contract issues. The evaluation scales from individual files to entire repositories, providing structured findings with precise locations and recommended fixes.

What is the best way to surface maintainability issues in an existing codebase?

The best way to surface maintainability issues is performing a deep structural review. This systematically evaluates code structure, dependencies, and error handling, returning actionable findings with severity and problem descriptions to guide fixes.

Do I need any dependencies to perform a deep code review on my repository?

No dependencies are required to perform a deep code review on your repository. The evaluation is self-contained and systematically checks error handling, edge cases, and concurrency without needing external components.