profile-coverage

Review profiler instrumentation coverage and classify uninstrumented functions by hot path relevance.

1|Updated Jan 12, 2026

Search Tags:#debugging #code coverage #profiling #instrumentation #performance analysis #hot path

Ready to run

npx skills add https://github.com/cwilliams5/Alt-Tabby --skill profile-coverage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: profile-coverage
Source: https://github.com/cwilliams5/Alt-Tabby/tree/main/.claude/skills/profile-coverage
Command: npx skills add https://github.com/cwilliams5/Alt-Tabby --skill profile-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify gaps in code instrumentation for performance profiling, ensuring that critical code paths are accurately measured.

Core Features & Use Cases

Instrumentation Map Generation: Creates a map of all functions and their current instrumentation status.
Gap Analysis: Classifies uninstrumented functions based on their relevance to the hot path or potential for blocking/delaying execution.
Use Case: A developer can use this Skill to quickly understand which parts of the application are not being profiled, allowing them to prioritize adding instrumentation for better performance insights.

Quick Start

Run the profile-coverage skill to review profiler instrumentation coverage and recommend new instrumentation points.

Frequently Asked Questions about profile-coverage

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

FAQPage Schema

How do I find gaps in code instrumentation for performance profiling?▼

To find gaps in code instrumentation for performance profiling, generate an instrumentation map that classifies uninstrumented functions based on their relevance to the hot path, marking them as 'YES', 'MAYBE', or 'NO' for new instrumentation points.

What is the best way to identify uninstrumented functions on a hot path?▼

The best way to identify uninstrumented functions on a hot path is to review profiler instrumentation coverage within specified source directories, analyzing function bodies and public APIs to classify missing measurement points by execution relevance.

Can I review instrumentation coverage for D3D11 and compositor pipelines?▼

Yes, you can review instrumentation coverage for D3D11 and compositor pipelines. The analysis specifically identifies these detailed pipeline areas for targeted review to ensure critical rendering paths are accurately measured.

How do I prioritize which functions need profiling instrumentation?▼

You prioritize which functions need profiling instrumentation by analyzing function bodies and public APIs to assess their potential for blocking or delaying execution, then classifying each uninstrumented function as 'YES', 'MAYBE', or 'NO'.

When do I need to review profiler instrumentation across my source code?▼

You need to review profiler instrumentation across your source code when performance analysis lacks accuracy, ensuring critical code paths are measured by mapping all functions and adding instrumentation to unprofiled hot path areas.