tester-detective

Identify test coverage gaps via AST-based callers analysis.

2|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/tianzecn/myclaudecode --skill tester-detective
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tester-detective
Source: https://github.com/tianzecn/myclaudecode/tree/main/plugins/code-analysis/skills/tester-detective
Command: npx skills add https://github.com/tianzecn/myclaudecode --skill tester-detective

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires claudemem, and includes references (resource) components.

What problem does it solve?

This Skill helps you audit test coverage, identify gaps, and understand which tests exercise which production code, without relying on traditional grep-based searches.

Core Features & Use Cases

  • Test Coverage Mapping: reveal which production symbols are covered by tests and which are not.
  • Gap Prioritization: surface high-importance untested code by PageRank-like significance.
  • Quality Guidance: provide insights into edge cases and test quality based on AST-call relationships.

Quick Start

Use the tester-detective skill to audit test coverage for a given module, then read the produced report to prioritize test work.

Frequently Asked Questions about tester-detective

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

FAQPage Schema
How do I identify untested functions in my codebase?

Test-coverage detective analyzes function-call relationships using AST to map which production code is exercised by tests and which is not, surfacing gaps without grep-based searching.

What's the best way to prioritize which tests to write first?

The Skill applies PageRank-like significance analysis to untested code, prioritizing high-importance gaps so you focus test efforts on the most critical uncovered functions.

Can I audit test coverage without running the full test suite?

Yes. The Skill uses AST-based callers analysis to build test-call mappings and coverage reports by analyzing code structure, not execution, making it fast for large codebases.

How does AST-based coverage analysis differ from traditional grep approaches?

AST parsing understands actual function calls and dependencies across your code, revealing coverage patterns that text search misses and avoiding false positives from comments or strings.

What dependencies do I need to use this Skill?

The Skill requires claudemem v0.3.0 for AST-based callers analysis. It forbids grep, find, and glob tools, relying instead on structured code-relationship mapping.

Can I use this Skill to detect edge cases in untested code?

Yes. By analyzing test-call relationships, the Skill provides quality guidance on edge cases and helps assess test quality based on which production paths are actually exercised.