codeprobe-performance

Detects and scores severity of performance and scalability issues in codebases.

4|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/nishilbhave/codeprobe --skill codeprobe-performance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codeprobe-performance
Source: https://github.com/nishilbhave/codeprobe/tree/main/skills/codeprobe-performance
Command: npx skills add https://github.com/nishilbhave/codeprobe --skill codeprobe-performance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill detects and scores performance and scalability issues across codebases, helping teams identify hotspots before they become outages.

Core Features & Use Cases

  • N+1 Queries: detect lazy loading inside loops without eager loading.
  • Missing Indexes: identify queries that would benefit from indexes.
  • Unbounded Queries: warn on operations that fetch entire datasets without pagination.
  • Memory & Caching: flag memory-heavy patterns and cache inefficiencies.
  • Frontend Performance: catch render or bundle-size issues impacting UX.
  • Use Case: run a full audit on a web app to surface critical hotspots and generate actionable fixes.

Quick Start

Run a performance audit on your project to emit a severity-scored report.

Frequently Asked Questions about codeprobe-performance

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

FAQPage Schema
How do I find N+1 queries and missing indexes in my codebase?

Run a performance audit to detect and score N+1 queries and missing indexes. The analysis covers lazy loading inside loops and identifies queries that would benefit from indexes, producing a severity-scored report with actionable fix prompts.

Can I run a performance audit on both Python and TypeScript code?

Yes, performance audits apply to both backend and frontend stacks across Python, TypeScript, and PHP. The analysis detects memory usage, caching, concurrency, and frontend render or bundle-size issues across these languages.

What is the best way to identify unbounded queries before a release?

Run a pre-release health check to warn on unbounded queries fetching entire datasets without pagination. This audit surfaces critical hotspots and generates actionable fix prompts to prevent scalability issues.

How does the code audit score performance and scalability issues?

The code audit scores performance and scalability issues by severity across N+1 queries, memory usage, caching, and concurrency. It produces a structured report with severity-scored findings and actionable fix prompts for each detected hotspot.

Does the performance analysis detect frontend render and bundle-size issues?

Yes, the performance analysis catches frontend render or bundle-size issues impacting UX. It flags memory-heavy patterns and cache inefficiencies, providing severity scores and fix prompts for frontend performance hotspots.

Why should I use an automated performance audit instead of manual code review?

An automated performance audit detects and scores issues across N+1 queries, missing indexes, and concurrency that manual reviews often miss. It emits a structured report with severity-scored findings and actionable fix prompts for faster remediation.