agents/skills/perf/SKILL.md
Before/after performance benchmarking comparing current branch against base, with statistical analysis. Use for benchmarking, profiling, or measuring performance impact.
npx skillsauth add drn/dots perfInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Run a command multiple times on the current branch and the base branch, then compare with statistical analysis.
$ARGUMENTS - Required: the command to benchmark (e.g., "go test -bench=. ./pkg/..." or "npm run build"). Optional: --runs <count> for number of runs (default 5), --base <ref> to override base branch.git branch --show-currentgit branch -r 2>/dev/null | grep -oE 'origin/(main|master)' | head -1git status --shortRun before/after benchmarks comparing the current branch against the base branch.
Extract the benchmark command and optional flags (--runs N, --base <ref>) from $ARGUMENTS.
IF no command is provided, ask: "What command should I benchmark?"
Resolve the script path — use the first that exists:
~/.claude/skills/perf/scripts/perf.sh (deployed via symlink)agents/skills/perf/scripts/perf.sh (repo-relative, for development/workspaces)bash <script-path> "<command>" [--runs N] [--base <ref>]
Handle the exit code:
<command>"Parse the script's structured output and present it as:
## Benchmark Results
**Command:** `<command>`
**Runs:** <N> (+ 1 warmup)
### Timing
| Metric | Base (<ref>) | Current (<branch>) | Delta |
|--------|-------------|-------------------|-------|
| Min | <X>s | <Y>s | <diff> |
| Max | <X>s | <Y>s | <diff> |
| Mean | <X>s | <Y>s | <diff> |
| Median | <X>s | <Y>s | <diff> |
| Stddev | <X>s | <Y>s | — |
### Raw Data
**Base:** <comma-separated times>
**Current:** <comma-separated times>
### Verdict: <REGRESSION / IMPROVEMENT / NEUTRAL>
<1-2 sentence explanation>
If the script output includes a high-variance warning, append it after the verdict.
development
Walk every unresolved review thread on a PR, triage each one, reply with a rationale of whether or not the comment will be acted upon, make the code change if warranted, and mark the thread resolved. Use when the user asks to address only the open PR comments without re-running CI, respond to review feedback, resolve review threads, or clear bot comments on a PR.
tools
Iteratively run /rereview, fix the findings, and loop until reviewers approve clean. Use for iterative automated review, when you want /rereview to loop until clean, or for a paranoid pre-merge review that auto-addresses every blocker.
development
Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.
development
Create reviewed Codex goal setup packages for long-running /goal work. Use when the user wants to turn an idea, backlog, project mission, or vague objective into durable goal files under a project goals slug folder, with Plannotator review gates for brief, narrative plan with acceptance criteria, verification, blockers, and the final /goal prompt.