القائمة
Review code for performance issues and run benchmarks. Use when user asks to analyze performance, run benchmarks, or review code for optimization opportunities.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Check and process messages from autonomous agents. Use when starting a session, after agent handoffs, or when checking for completion notifications. This skill describes the pattern of inter-agent messaging -- adapt the implementation to your project's tooling.
Set up Claude Code cloud/mobile environments for development. Use when starting a new cloud session, when tools are missing, or when user says "setup cloud", "setup environment", or mentions mobile Claude Code.
Monitor and refactor large files into smaller, AI-friendly modules. Use when user asks to check file sizes, split large files, or organize the codebase. Ensures tests pass before and after refactoring.
Create design documents in the correct format and location. Use when user asks to create a design doc, plan a feature, or document a design. Handles both planned/ and implemented/ docs with proper structure.
Monitor and triage GitHub issues against design docs and implementation status. Use when user asks to "check issues", "triage issues", "sync issues", "what issues are open", or wants to ensure issues are up-to-date with development progress.
Run Claude Code in headless/programmatic mode for automation, CI/CD, and agent workflows. Use when user asks about headless mode, programmatic execution, scripting Claude, or automating Claude workflows.
| name | Perf Reviewer |
| description | Review code for performance issues and run benchmarks. Use when user asks to analyze performance, run benchmarks, or review code for optimization opportunities. |
Review code for performance issues and run benchmarks.
| Environment Variable | Default | Description |
|---|---|---|
BUILD_CMD | make build | Command to build the project |
TEST_CMD | make test | Command to run tests |
BENCHMARK_CMD | make bench | Command to run benchmarks |
# Run benchmarks
scripts/benchmark.sh
# Run specific benchmark
scripts/benchmark.sh fibonacci
# Review code for performance issues
# Just ask: "review this code for performance"
Invoke this skill when:
scripts/benchmark.sh [benchmark_name]Run benchmarks comparing different implementations or configurations.
Available benchmarks: fibonacci, sum, all
Output: Timing comparisons, speedup ratios, and recommendations.
When reviewing code, check against these principles (see resources/principles.md):
Critical checks:
Quick checklist:
[ ] No O(n^2) where O(n log n) exists
[ ] Batch APIs for repeated operations
[ ] Allocations hoisted outside loops
[ ] Hot paths optimized, edge cases separate
[ ] No unnecessary string formatting in loops
# Full benchmark suite
scripts/benchmark.sh all
# Single benchmark
scripts/benchmark.sh fibonacci
Use your language's profiling tools to identify actual bottlenecks before optimizing.
From resources/principles.md:
| Principle | Action |
|---|---|
| Profile First | Measure before optimizing |
| Algorithms > Micro-opts | O(n) beats optimized O(n^2) |
| Batch Operations | Amortize overhead |
| Memory Layout | Cache-friendly structures |
| Fast Path | Optimize common case |
| Defer Work | Lazy evaluation |
| Right-size Data | Appropriate containers |