mcpField
I
inspect-perf

inspect-perf

github.com/venhdevTesting & quality158 installsUpdated 1d ago
Repository

About inspect-perf

inspect-perf is a code-auditing skill for developers assessing performance and resource efficiency in a specified file, directory, or subsystem. It applies a performance rubric to structural risks, separates local fixes from architectural changes, and stops when no target scope is provided.

Key features

  1. 01Requires an explicit audit scope
  2. 02Checks algorithmic and I/O risks against a rubric
  3. 03Ignores micro-benchmark-level optimizations
  4. 04Separates local fixes from architectural refactors
  5. 05Produces a structured performance dossier

Use cases

  1. 01Audit algorithms and resource use in a module
  2. 02Find code paths that may multiply I/O
  3. 03Route performance findings to an appropriate remediation

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/venhdev/skills --skill inspect-perf

After installing, type/inspect-perfin Claude Code to confirm it loaded.

Bundled filesreferences/performance-rubric.md

Details

From the project README

inspect-perf — Semantic Performance & Resource Efficiency Auditor

Domain Rubric

1. Scope & Tolerability Guardrails (What to Ignore)
  • Mandatory Target Scope: The user MUST specify an explicit target path (file, directory, or subsystem). If no target scope is provided, halt turn immediately and prompt for scope; forbid speculative full-repository scans.
  • Semantic Debt vs. Micro-Benchmarking: Confine analysis strictly to structural algorithmic risks, I/O multipliers, and resource retention; ignore sub-microsecond instruction micro-optimizations, compiler inlining nits, or premature caching on cold paths.
  • Governing Reference: Evaluate performance patterns strictly against references/performance-rubric.md.
2. Decision Bifurcation: [LOCAL-FIX] vs. [ARCHITECTURAL-REFACTOR]
  • [LOCAL-FIX] (Localized In-Function Optimization): Algorithmic lookup indexing ($O(1)$ set/map), loop invariant hoisting, or string builder replacement within a single method/file. Route behavior-preserving candidates to /simplify-audit; new query limits or altered result semantics require /changeset.
  • [ARCHITECTURAL-REFACTOR] (Systemic Structural Remediation): Decomposing Cartesian joins into Split Queries / DataLoaders, extracting Transactional Outbox to decouple network I/O from database transactions, worker thread offloading, or introducing bounded distributed caches. Route remediation to /changeset.

Canonical Output Contract

# Performance Audit Dossier: <Target Scope>

## 1. Executive Summary
- **Target Inspected**: `<directory_or_file_path>`
- **Health Rating**: <OPTIMAL | LOCALIZED_BOTTLENECK | CRITICAL_DEGRADATION>
- **Primary Bottleneck**: <Single-sentence summary of highest-latency or highest-risk resource hazard>

## 2. Load-Bearing Defect Catalog
### [<CRITICAL | MAJOR>] [<LOCAL-FIX | ARCHITECTURAL-REFACTOR>] <Dimension>: `<Target Symbol / Query>`
- **Offending Code**: [<file>#L<N>](file:///path/to/file#L<N>)
- **Violated Rubric**: [<spec_or_dimension>](references/performance-rubric.md#anchor)
- **Smell**: <Observable bottleneck, complexity multiplier, or resource leak description>
- **Action**: <[LOCAL-FIX] Local optimization OR [ARCHITECTURAL-REFACTOR] Separation / batching path>

*(Emit 'No load-bearing performance defects observed across rubric dimensions' if clean)*
Routing
  • Local indexing or builder changes whose behavior equivalence can be audited → (via /simplify-audit).
  • Changes to result semantics or systemic split-query, outbox, connection-pool, or thread-pool refactorings → (via /changeset).

Execution Protocol

  1. Intake & Scope Gate:

    • Ingest target scope (file, directory, or subsystem).
    • Enforce Scope Gate: If no explicit scope is provided, halt turn immediately and prompt user: "Vui lòng chỉ định rõ phạm vi kiểm tra (file, thư mục hoặc subsystem) khi sử dụng /inspect-perf."
    • Read and ground in references/performance-rubric.md.
  2. Scale-Adaptive Pragmatic Audit:

    • In-Turn Execution (< 10 files or cohesive module): Audit code directly in-turn against rubric dimensions.
    • Subagent Fan-Out (broad multi-package subsystem): Launch 2–3 research subagents (Role: Performance Inspector (<Slice>)) seeded with slice coordinates, discovered anchors, Domain Rubric, and Output Contract.
    • Enforce Section 1 Guardrails: ignore micro-benchmarking noise on non-hot paths; classify every finding explicitly as [LOCAL-FIX] or [ARCHITECTURAL-REFACTOR].
  3. Synthesis & Turn-Halt Gate:

    • Consolidate findings into the Canonical Output Contract.
    • Assign definitive Health Rating (OPTIMAL, LOCALIZED_BOTTLENECK, CRITICAL_DEGRADATION).
    • Present completed dossier into conversation stream and halt turn immediately.

Comments

Markdown supported