phargus-verify

Original：🇺🇸 English

Translated

7 scripts

Verify a Node.js performance or memory fix by comparing Phargus measurements before and after the change. Use when deciding whether a runtime change helped, regressed, or remains inconclusive.

2installs

Sourcepharn-dev/skills

Added on2026-10-25

NPX Install

npx skill4agent add pharn-dev/skills phargus-verify

SKILL.md Content

View Translation Comparison →

Phargus Verify

Determine whether the requested change achieved its runtime goal. Read verification and data semantics. Use tools for capture, summarize and compare.

Establish the goal and baseline before editing code or running the after measurement. Resolve this skill's absolute directory; invoke its scripts/phargus.mjs there.
Record workload, concurrency, requests, warmupMs, durationMs, nodeVersion, machine, intervalMs and windowMs in capture conditions. Record application/config revisions.
Reproduce matching conditions after the change. Keep both data files and manifests.
Run compare with both manifests. Different conditions, missing data, truncation or unknown loss yield an inconclusive result; obtain a controlled raw capture to resolve it. Live capture stops at 10,000 events by default: for a high-rate service pass --max-events or a shorter --duration-ms. compare reads files without an event-count cap.
For comparable measurements, assess deltas against the goal and inspect collateral heap/RSS, GC and backpressure changes. Repeat if normal variation can change the verdict.

Return before/after values, conditions, quality and a justified verdict with remaining uncertainty. A smaller number under lower load does not establish improvement. Read compatibility before requesting unsupported profiling.

Example request: "Verify that replacing this synchronous handler improved runtime latency."

phargus-verify

NPX Install

Tags

SKILL.md Content

Phargus Verify