swarm-performance-agent

Identify performance bottlenecks in gnubok's codebase without modifying files.

209|46|Updated Feb 13, 2026

Search Tags:#performance #rendering #audit #bundle-size #n+1-queries #gnubok

Ready to run

npx skills add https://github.com/erp-mafia/gnubok --skill swarm-performance-agent

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: swarm-performance-agent
Source: https://github.com/erp-mafia/gnubok/tree/main/.claude/skills/swarm-performance-agent
Command: npx skills add https://github.com/erp-mafia/gnubok --skill swarm-performance-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only audit agent that identifies gnubok performance bottlenecks without modifying code, enabling teams to prioritize optimizations with evidence.

Core Features & Use Cases

Sweep app//*.tsx, app//.jsx, app/api/**/.ts, lib/**/*.ts to surface bundle and query inefficiencies.
Detect large images/assets, blocking imports, unnecessary re-renders, and fetchAllRows misuse.
Provide actionable findings suitable for development and operations workflows.

Quick Start

Initiate a non-invasive performance sweep across the repository to surface bottlenecks.

Frequently Asked Questions about swarm-performance-agent

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

FAQPage Schema

How do I audit performance bottlenecks without modifying existing code?▼

You can audit performance bottlenecks by running a read-only sweep across your repository paths to detect bundle size inflation, N+1 queries, and blocking imports without altering any files.

What causes bundle size inflation and N+1 queries in a React codebase?▼

Bundle size inflation and N+1 queries often stem from large images, blocking imports, unnecessary re-renders, and fetchAllRows misuse across your app and lib directories.

How do I detect unnecessary re-renders and heavy main-thread work in my application?▼

To detect unnecessary re-renders and heavy main-thread work, analyze front-end rendering paths by sweeping tsx and jsx files to surface inefficiencies and actionable findings.

Can I run a non-invasive performance audit on server and data-access paths?▼

Yes, you can run a non-invasive performance audit on server and data-access paths by analyzing api and lib typescript files to identify query inefficiencies while adhering to read-only constraints.

What are the limitations of a read-only performance sweep?▼

A read-only performance sweep is limited to identifying bottlenecks and providing actionable insights, meaning it cannot automatically fix or modify the detected bundle and query issues.