perf

Detect performance regressions in code changes via static analysis and optional benchmarks.

82|23|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Rune-kit/rune --skill perf-rune-kit
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: perf
Source: https://github.com/Rune-kit/rune/tree/main/skills/perf
Command: npx skills add https://github.com/Rune-kit/rune --skill perf-rune-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

šŸ’” This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill acts as a crucial gatekeeper, identifying performance regressions like N+1 queries, sync-in-async issues, missing indexes, memory leaks, and bundle bloat before they impact production.

Core Features & Use Cases

  • Proactive Detection: Catches common performance anti-patterns in code changes.
  • Multi-faceted Analysis: Examines database queries, asynchronous code, memory usage, and frontend bundle sizes.
  • Use Case: Before merging a new feature, run /rune perf to ensure it doesn't introduce slow database queries or increase frontend load times, preventing user-facing performance degradation.

Quick Start

Run the perf skill to analyze the current code changes for performance regressions.

Frequently Asked Questions about perf

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

FAQPage Schema
How do I detect N+1 queries and database index issues before merging code?ā–¼

Detecting N+1 queries and missing database indexes involves running performance regression analysis on code changes. This Skill scans file lists or identified hotpaths to catch slow database queries and missing indexes before they impact production.

What is the best way to prevent frontend bundle bloat during development?ā–¼

Preventing frontend bundle bloat requires analyzing code changes for performance regressions. This Skill examines frontend bundle sizes and can optionally run Lighthouse audits to ensure new features do not increase frontend load times.

How do I check for sync-in-async operations and memory leaks in my code?ā–¼

Checking for sync-in-async operations and memory leaks involves performing multi-faceted performance analysis. This Skill examines asynchronous code and memory usage to identify anti-patterns in your current code changes.

Can I run Lighthouse audits and benchmarks automatically when checking performance regressions?ā–¼

You can optionally run benchmarks and Lighthouse audits when checking performance regressions. This allows you to measure frontend load times and validate that new features do not introduce user-facing performance degradation.

Does performance regression analysis work for both frontend and backend code?ā–¼

Yes, performance regression analysis works for both frontend and backend code. It scopes analysis based on file lists or hotpath identification, performing framework-specific checks for database queries, async operations, and bundle bloat.