Perf Code Paths
- 62 installs
- 931 repo stars
- Updated July 26, 2026
- avifenesh/agentsys
perf-code-paths is a Claude Code skill that maps entrypoints and likely hot files and symbols for a performance scenario before profiling.
About
perf-code-paths identifies the likely implementation paths for a performance scenario before profiling starts. It uses repo intelligence or grep to find entrypoints and handlers, then lists the top candidate files and symbols tied to the scenario with a short reason for each. A developer uses it to narrow where to profile so time is not wasted. It focuses on Rust, Java, JS/TS, Go and Python and keeps to the most relevant 10 to 15 files.
- Maps likely hot files, entrypoints and symbols before profiling
- Uses repo-intel or grep for entrypoints and handlers
- Supports Rust, Java, JS/TS, Go and Python and keeps to the top 10-15 files
Perf Code Paths by the numbers
- 62 all-time installs (skills.sh)
- Ranked #289 of 596 Debugging skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
perf-code-paths capabilities & compatibility
- Capabilities
- perf profiler · perf benchmarker · perf analyzer
- Use cases
- debugging · research
What perf-code-paths says it does
Identify likely implementation paths for a performance scenario.
Use repo-intel if available; otherwise use grep for entrypoints and handlers.
Focus only on supported languages (Rust, Java, JS/TS, Go, Python).
npx skills add https://github.com/avifenesh/agentsys --skill perf-code-pathsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 62 |
|---|---|
| repo stars | ★ 931 |
| Last updated | July 26, 2026 |
| Repository | avifenesh/agentsys ↗ |
What it does
Map the likely hot files and symbols for a perf scenario before profiling.
Who is it for?
Narrowing the profiling target to the most relevant files and symbols.
Skip if: Actually running the profiler or benchmarks.
When should I use this skill?
You are mapping code paths, entrypoints, and likely hot files before profiling.
What you get
- A keyword list and candidate file/symbol paths with evidence
By the numbers
- Keeps to the most relevant 10-15 files
- Supports 5 languages (Rust, Java, JS/TS, Go, Python)
Files
perf-code-paths
Identify likely implementation paths for a performance scenario.
Follow docs/perf-requirements.md as the canonical contract.
Required Steps
1. Use repo-intel if available; otherwise use grep for entrypoints and handlers. 2. List top candidate files/symbols tied to the scenario. 3. Include imports/exports or call chains when relevant.
Output Format
keywords: <comma-separated list>
paths:
- file: <path>
symbols: [<symbol1>, <symbol2>]
evidence: <short reason>Constraints
- Focus only on supported languages (Rust, Java, JS/TS, Go, Python).
- Keep to the most relevant 10-15 files.
Related skills
Azure DiagnosticsSystematically diagnose and resolve production issues on Microsoft Azure using official Microsoft guidance.495k1.3kAzure MessagingQuickly diagnose and fix connection, authentication, and message-processing failures when using Azure Event Hubs or Service Bus SDKs.483k1.3k
Diagnosing BugsGet a systematic, step-by-step process that surfaces the real root cause instead of guessing at bugs.291k200k
Use My BrowserWhen their agent task requires access to the live browser session, rendered DOM state, authenticated dashboards, localhost apps, or DevTools-selected elements instea269k71
Systematic DebuggingFollow a repeatable four-phase process that forces root-cause discovery before any code changes.210k265k
Safe DebugGet conservative, non-destructive diagnosis of deep learning and agent errors before any code changes are made.185k512