Perf Code Paths
- 2 installs
- 931 repo stars
- Updated July 26, 2026
- avifenesh/awesome-slash
perf-code-paths is a skill that maps the entrypoints and likely hot files for a performance scenario before profiling.
About
This skill identifies the likely implementation paths for a performance scenario before profiling begins. A developer uses it to narrow a codebase to the entrypoints, handlers, and hot files worth investigating. It leans on repo-intel data when available or falls back to grep, and it lists candidate files with symbols and short evidence.
- Maps code paths, entrypoints, and likely hot files before profiling
- Uses repo-intel when available or grep for entrypoints and handlers
- Focuses on Rust, Java, JS/TS, Go, and Python and the top 10-15 relevant files
Perf Code Paths by the numbers
- 2 all-time installs (skills.sh)
- Ranked #464 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
- code path mapping · static analysis · profiling prep
- 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/awesome-slash --skill perf-code-pathsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 931 |
| Last updated | July 26, 2026 |
| Repository | avifenesh/awesome-slash ↗ |
What it does
Map the likely hot files, entrypoints, and symbols for a performance scenario before profiling.
Who is it for?
Developers narrowing a large codebase to the files worth profiling for a specific slow scenario.
Skip if: Actually profiling or benchmarking; this skill only locates candidate code paths.
When should I use this skill?
You are mapping code paths, entrypoints, and likely hot files before profiling.
What you get
A short list of candidate files and symbols with evidence, ready to profile.
- candidate file/symbol list
- keyword list
By the numbers
- keeps to 10-15 most relevant 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.185k512FAQ
Which languages does it support?
Rust, Java, JS/TS, Go, and Python only.
How many files does it return?
It keeps to the most relevant 10 to 15 files for the scenario.