Ultrathink Detective FAQs

Question 1

Why does this skill forbid the use of grep and find?

Accepted Answer

Grep and find are text-based and lack structural context. Ultrathink Detective uses AST analysis via claudemem to understand relationships, call chains, and symbol importance, which is far more accurate for complex audits.

Question 2

How does it identify test coverage gaps?

Accepted Answer

The skill analyzes 'callers' for critical functions; if a high-importance symbol has zero callers from test files (like *.test.ts), it flags it as a critical coverage gap.

Question 3

Is there a prerequisite for using this skill?

Accepted Answer

Yes, claudemem v0.3.0 or higher must be installed and the codebase must be indexed to enable the AST structural analysis commands.

Question 4

What model is recommended for Ultrathink Detective?

Accepted Answer

This skill is specifically designed for the Opus model to provide the maximum reasoning depth and strategic analysis required for multi-dimensional investigations.

Question 5

What is the role of PageRank in this skill?

Accepted Answer

PageRank identifies the most 'central' pieces of code in your repository. This allows the detective to prioritize the analysis of architectural pillars that have the most impact on system stability.

Ultrathink Detective

Key Features

Use Cases

Ultrathink Detective

Key Features

Use Cases