perf-code-paths

Map code paths and entrypoints to identify hot files and call chains.

1.9k|545|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-plugins --skill perf-code-paths
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perf-code-paths
Source: https://github.com/ComposioHQ/awesome-claude-plugins/tree/main/perf/skills/code-paths
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-plugins --skill perf-code-paths

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill maps code paths and entrypoints to guide profiling efforts, reducing guesswork and speeding optimization.

Core Features & Use Cases

  • Path mapping: Identify likely implementation paths and entrypoints to focus profiling.
  • Candidate listing: Produce a concise list of top files and symbols with evidence.
  • Use Case: Imagine profiling a microservice in Go or a Node.js app; this Skill highlights the top hot files and call chains to inspect first.

Quick Start

Run perf-code-paths on your repository to generate a prioritized list of candidate files and symbols for profiling.

Frequently Asked Questions about perf-code-paths

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

FAQPage Schema
How do I find hot code paths and entrypoints for profiling?

Identifying entrypoints for profiling requires scanning available repository maps to trace call chains, producing a structured list of the 10-15 most relevant candidate files with symbols and evidence.

Can I analyze code paths for performance issues in Go and Python?

Yes, you can analyze code paths for performance issues across Rust, Java, JS/TS, Go, and Python to identify likely implementation paths and focus your profiling efforts.

What is the best way to identify hot files before starting performance profiling?

The best way to identify hot files is by mapping code paths and entrypoints to generate a concise candidate listing of top files and symbols with evidence, reducing guesswork.

Does perf-code-paths work without external profiling dependencies?

Yes, perf-code-paths operates with no external dependencies, using available repo maps or entry-point scans to guide your performance profiling efforts directly.

How many candidate files does the code path analysis produce?

The code path analysis produces a structured list focusing on the 10-15 most relevant candidate files, complete with symbols and evidence to guide profiling.

When should I map code paths instead of running a profiler directly?

Mapping code paths is essential when you need to reduce guesswork by identifying likely implementation paths and entrypoints first, ensuring your profiler targets the correct hot files and call chains.