investigate

Name: investigate
Availability: InStock
Author: Aibility

Trace evidence trails to uncover root causes and bugs across systems.

1|Updated Mar 8, 2026

Search Tags:#architecture #performance #debugging #investigate #code-analysis #root-cause

Ready to run

npx skills add https://github.com/aibilitycz/superpowered-toolkit --skill investigate-aibilitycz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/aibilitycz/superpowered-toolkit/tree/main/plugins/super-intelligence/skills/investigate
Command: npx skills add https://github.com/aibilitycz/superpowered-toolkit --skill investigate-aibilitycz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detectives-style investigation that follows evidence trails to find root causes, bugs, inconsistencies, and hidden problems across code, performance, architecture, data, and systems. Three investigative lenses: Sherlock Holmes (deduction), Hercule Poirot (psychology/intent), Columbo (what's missing).

Core Features & Use Cases

Phase-driven workflow (Phase 0–6) for repeatable investigations.
Three minds to surface premises, intent gaps, and missing edge cases.
Auto-generated case reports and read-only guidance to inform decisions.

Quick Start

Describe the issue, select the relevant domains, and start Phase 0 to establish the case.

Frequently Asked Questions about investigate

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

FAQPage Schema

How do I find the root cause of a performance regression in my codebase?▼

To find the root cause of a performance regression, this investigation systematically traces evidence trails across code, architecture, and data using a structured workflow. It applies detective-style analysis to uncover hidden defects and design gaps, outputting a detailed case report.

What is the best way to debug architectural inconsistencies across systems?▼

Debugging architectural inconsistencies is best handled by applying three investigative lenses—deduction, intent analysis, and edge-case discovery—to systematically surface hidden problems. It evaluates code and deployments to identify structural design gaps and present actionable findings.

How do I trace a defect through a data pipeline step by step?▼

To trace a defect through a data pipeline, start at Phase 0 to establish the case, then follow the evidence trail across systems using read-only access. The workflow systematically uncovers bugs and inconsistencies, concluding with an auto-generated case report.

Can I investigate production issues without write access to the deployment?▼

Yes, you can investigate production issues with read-only access using tools like Read, Grep, and Glob. The investigation requires only read-only guidance to systematically uncover root causes and inform decisions without modifying the deployment environment.

When should I use a structured investigation workflow for code analysis?▼

Use a structured investigation workflow for code analysis when tracing complex defects, performance regressions, or design gaps across codebases and systems. It is necessary when you need repeatable, phase-driven detective analysis to surface hidden problems and intent gaps.