perf-check

Identify performance hotspots and regressions in Loom-style codebases.

2|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/Nickalus12/Loom --skill perf-check-nickalus12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perf-check
Source: https://github.com/Nickalus12/Loom/tree/main/claude/skills/perf-check
Command: npx skills add https://github.com/Nickalus12/Loom --skill perf-check-nickalus12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you quickly identify performance hotspots, regressions, and optimization opportunities in your Loom-style projects, enabling targeted improvements.

Core Features & Use Cases

  • Define performance targets and baselines for code paths or modules.
  • Identify hotspots, compare against baselines, and prioritize optimizations.
  • Use case: when optimizing a slow module, generate a plan with suggested changes and metrics.

Quick Start

Run a performance-assessment workflow on your codebase to surface hotspots and actionable optimizations.

Frequently Asked Questions about perf-check

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

FAQPage Schema
How do I identify performance hotspots and regressions in a Loom-style codebase?

You can identify hotspots and regressions by running a performance-assessment workflow that establishes baselines, compares current metrics against them, and prioritizes optimization opportunities across target modules.

How do I establish performance baselines for specific code paths before optimizing?

You establish baselines by applying the assessment to specific code paths or modules, gathering current metrics to define targets that guide future code-analysis and measurements.

Can I use this to generate an optimization plan for a slow module?

Yes, you can generate an actionable optimization plan for a slow module that outlines analysis steps, suggests specific changes, and defines metrics to measure improvements against the baseline.

What is the best way to prioritize code optimizations after gathering baseline metrics?

The best way to prioritize optimizations is to compare identified hotspots against established baselines, focusing on code paths with the highest regression to produce actionable recommendations.

Do I need specific dependencies to perform a performance assessment on my code?

No specific dependencies are required to perform the performance assessment, as the workflow operates directly on the target codebase to surface hotspots and outline optimization steps.