build-perf-audit

Profile build systems and rank hotspots by wall time and frequency.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/marcelocantos/skills --skill build-perf-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-perf-audit
Source: https://github.com/marcelocantos/skills/tree/main/skills/build-perf-audit
Command: npx skills add https://github.com/marcelocantos/skills --skill build-perf-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long or flaky local and CI builds slow developer iteration and block delivery by hiding hotspots, misconfigured caching, and suboptimal parallelism; this Skill uncovers the root causes and drives measurable speed improvements.

Core Features & Use Cases

  • Baseline profiling: measure clean, no-op incremental, and one-file-change incremental build times with per-step breakdowns to establish a reliable benchmark.
  • Hotspot analysis & pattern matching: rank steps by wall time × frequency and match them against cross-cutting and system-specific anti-patterns to identify high-impact fixes.
  • Propose, apply, and verify fixes: generate prioritized, measurement-backed recommendations, optionally auto-apply low-risk changes, and verify correctness with artifact checks and before/after measurements.
  • Use case: when CI wall-time drifts upward or local developer iteration is slow, run the Skill to find caching gaps, serial bottlenecks, or misconfigured build flags and deliver a report plus safe remediation steps.

Quick Start

Run the build-perf-audit skill against your repository to profile the primary build, surface hotspots, and receive prioritized, measurable fixes.

Frequently Asked Questions about build-perf-audit

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

FAQPage Schema
How do I find bottlenecks and fix slow CI build times?

Audit build systems for performance regressions by profiling local builds and inspecting CI jobs to rank hotspots by wall time and frequency, generating measurement-backed proposals to cut CI build times.

What is the best way to profile incremental build performance across different tools?

Baseline profiling measures clean, no-op, and one-file-change incremental builds with per-step breakdowns to establish a reliable benchmark and identify hotspots across supported build systems.

Can I auto-apply optimizations for caching and parallelism issues found during a build audit?

Yes, build audit tools can optionally auto-apply low-risk changes to fix caching gaps and serial bottlenecks, then verify correctness with artifact checks and before/after measurements.

Does build performance profiling work with Bazel, Gradle, Cargo, and Node?

Yes, build performance profiling applies to repositories and CI pipelines across common systems including Make, Cargo, CMake, Gradle, Bazel, Node, Xcode, Go, and dotnet to find misconfigured build flags.

Why does CI wall-time drift upward and how do I measure the root cause?

CI wall-time drifts upward due to hidden hotspots, misconfigured caching, and suboptimal parallelism; you measure the root cause by generating per-step timings and matching them against anti-patterns.