DLC: Performance Analysis

Run performance checks against the current project and create a GitHub issue with findings.

Before running, read ../dlc/references/ISSUE-TEMPLATE.md now for the issue format, and read ../dlc/references/REPORT-FORMAT.md now for the findings data structure.

Step 1: Identify Performance-Sensitive Areas

Scan the project to determine which performance checks are applicable:

Indicator	Check Type	Tools
`webpack.config.` / `vite.config.` / `next.config.*`	Bundle analysis	`webpack-bundle-analyzer`, `vite-bundle-analyzer`, `@next/bundle-analyzer`
`lighthouse` in deps or CI config	Lighthouse	`lighthouse` CLI
`bench` / `benchmark` dirs or scripts	Benchmarks	Project-specific (e.g. `vitest bench`, `cargo bench`, `go test -bench`)
`docker-compose*` / `Dockerfile`	Container analysis	`dive`, `docker image inspect`
`tsconfig.json` / `package.json` (with build scripts)	Build time	Time the build command

Related skills

Installs

Repository

GitHub Stars

First Seen

Apr 20, 2026

Security Audits