scale-canary
Performance complexity and resource allocation canary — checks for O(N^2) loops, database N+1 query patterns, memory leaks (unbounded collections), and blocking calls in main event loop. Triggers on keywords: "/scale-canary", "scale-canary", "performance audit", "scale audit". Us
Install
npx skills add https://github.com/TheColliery/CoalMine/tree/main/skills/scale-canary
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install hetcreep-coalmine@llmmart
git clone https://github.com/TheColliery/CoalMine.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole hetcreep/coalmine collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Scale Canary (Performance & Resource Allocation Audit)
Audit code for scalability issues, performance bottlenecks, and resource leaks.
Auditing Categories
- O(N^2) Complexity — nested loops over growable collections without indexing or caching (crashes at scale).
- N+1 Database Queries — querying records in a loop instead of a batch JOIN or bulk prefetch.
- Memory Bloat / Leaks — appending to global arrays/maps without clearing them → unbounded growth.
- Blocking Main Loop — synchronous FS ops or CPU-heavy work on the main event thread (lag/hangs).
- Resource Leakage — streams, connections, or handles left open without a
finallyclose.
Per-ORM N+1 shapes, per-stack blocking patterns, and what NOT to flag: read references/checks.md before scanning.
Fix mode (choice-gated)
In Agent Context, after the report, present via ask_question:
- Apply safe optimizations: async-ify synchronous file ops; insert
finallyblocks for stream closing. Each fix: checkpoint (copy the touched file(s) aside, or use an isolated worktree — nevergit stash/git commit, which can hide or include unrelated staged/unstaged user work) → record a build+test BASELINE → apply → build + tests → auto-revert only if a NEW failure appeared versus the baseline. - Let me pick: user selects specific optimizations.
- Report only: exit unchanged.
Grants & denials (CLASSIFY-BLOCK)
| class | step it powers | grant | on denial |
|---|---|---|---|
| read | scan loops/queries/caches for the categories above | Read·Grep·Glob |
refuse that file, name it — never a clean bill |
| write | Fix mode's safe-optimization apply, incl. checkpoint → baseline → build+tests → auto-revert only on a NEW failure | Edit·Bash (checkpoint/build/revert need exec) |
report the fix as NOT applied AND the checkpoint/revert as NOT available, never claim done |
Output
| file:line | bottleneck | severity | finding | optimization plan |
Severity: CRITICAL (O(N^2) on user-facing API / unclosed file handles) · HIGH (N+1 query pattern / blocking main loop) · MEDIUM (unbounded cache growth) · LOW (minor efficiency suggestions)
Files (coalmine)
-
references
-
checks.md 2 KB
Loading…
-
-
skill-meta.json 195 B
Loading… -
SKILL.md 2.7 KB
--- name: scale-canary description: >- Performance complexity and resource allocation canary — checks for O(N^2) loops, database N+1 query patterns, memory leaks (unbounded collections), and blocking calls in main event loop. Triggers on keywords: "/scale-canary", "scale-canary", "performance audit", "scale audit". Use when writing loops over growing data, DB queries, caches, or async/event-loop code. --- # Scale Canary (Performance & Resource Allocation Audit) <!-- SHARED:LANGUAGE_HEADER --> Audit code for scalability issues, performance bottlenecks, and resource leaks. ## Auditing Categories 1. **O(N^2) Complexity** — nested loops over growable collections without indexing or caching (crashes at scale). 2. **N+1 Database Queries** — querying records in a loop instead of a batch JOIN or bulk prefetch. 3. **Memory Bloat / Leaks** — appending to global arrays/maps without clearing them → unbounded growth. 4. **Blocking Main Loop** — synchronous FS ops or CPU-heavy work on the main event thread (lag/hangs). 5. **Resource Leakage** — streams, connections, or handles left open without a `finally` close. Per-ORM N+1 shapes, per-stack blocking patterns, and what NOT to flag: read `references/checks.md` before scanning. ## Fix mode (choice-gated) In Agent Context, after the report, present via `ask_question`: - **Apply safe optimizations:** async-ify synchronous file ops; insert `finally` blocks for stream closing. Each fix: checkpoint (copy the touched file(s) aside, or use an isolated worktree — never `git stash`/`git commit`, which can hide or include unrelated staged/unstaged user work) → record a build+test BASELINE → apply → build + tests → auto-revert only if a NEW failure appeared versus the baseline. - **Let me pick:** user selects specific optimizations. - **Report only:** exit unchanged. ## Grants & denials (CLASSIFY-BLOCK) | class | step it powers | grant | on denial | |---|---|---|---| | read | scan loops/queries/caches for the categories above | `Read`·`Grep`·`Glob` | refuse that file, name it — never a clean bill | | write | Fix mode's safe-optimization apply, incl. checkpoint → baseline → build+tests → auto-revert only on a NEW failure | `Edit`·`Bash` (checkpoint/build/revert need exec) | report the fix as NOT applied AND the checkpoint/revert as NOT available, never claim done | <!-- SHARED:CLASSIFY_BLOCK --> ## Output `| file:line | bottleneck | severity | finding | optimization plan |` Severity: CRITICAL (O(N^2) on user-facing API / unclosed file handles) · HIGH (N+1 query pattern / blocking main loop) · MEDIUM (unbounded cache growth) · LOW (minor efficiency suggestions) <!-- SHARED:REPORTING_FOOTER --> <!-- SHARED:ORCHESTRATION --> <!-- SHARED:ESCALATION_FOOTER -->
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.