Overview

perf-code-paths identifies likely implementation paths for a performance scenario and prepares profiling targets by listing top candidate files and symbols. It follows perf-requirements and uses concise evidence to justify each path. The focus is on Rust, Java, JS/TS, Go, and Python with a manageable 10–15 file scope.

How This Skill Works

It uses repo-map if available; otherwise it greps for entrypoints and handlers. It then outputs a paths block containing file, symbols, and evidence, optionally including imports/exports or call chains when relevant.

When to Use It

• Before profiling a performance scenario, to pinpoint candidate files and symbols.
• When starting in a new repository to locate likely hot paths without profiling yet.
• When optimizing a specific feature or endpoint in a web app by mapping its call graph.
• For cross-language codebases to highlight hotspots across Rust, Java, JS/TS, Go, and Python.
• When you must cap the scope to the most relevant 10–15 files to keep analysis manageable.

Quick Start

1. Step 1: Use repo-map if available; otherwise grep for entrypoints and handlers.
2. Step 2: List the top candidate files and symbols tied to the scenario.
3. Step 3: Include imports/exports or call chains and format as per the Output Format.

Best Practices

• Use repo-map first to get precise paths.
• If repo-map isn't available, run grep for entrypoints and handlers methodically.
• Keep the results to 10–15 files or symbols.
• Include imports/exports or call chains where they clarify the path.
• Capture concise evidence for each path.

Example Use Cases

• Python FastAPI app: routes.py and main.py mapped to endpoints, evidenced by route decorators in routes.py.
• Node.js Express app: server.js and routes/auth.js, evidenced by app.post('/login', ...).
• Java Spring Boot: UserController.java and UserService.java, evidenced by @RequestMapping and service call chain.
• Rust Actix-web: main.rs and handlers/mod.rs, evidenced by route macro mapping to a handler function.
• Go net/http: server.go and handlers/user.go, evidenced by ServeMux patterns like /user/login.

Frequently Asked Questions