Design, review, or report a measured performance comparison. Use for benchmark methodology, speedup or regression claims, and performance-based choices; not generic performance discussion, ordinary dependency bumps, local renames, or prose edits.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Vet the claim against measured work. Use the existing benchmark harness and stay within the task's authority for runs, instrumentation, edits, and publication.
For a requested quick estimate, report the observed value, units, environment, reproduction command, errors and completed work, and label it as a single run without a comparison verdict. Missing correctness or work evidence makes even a quick estimate inconclusive.
For a formal comparison, finish with faster, slower, no measurable difference, or inconclusive; include run count, units, spread, environment, limiter evidence, and reproduction command. Mark missing correctness, work, fairness, or limiter evidence as inconclusive. Separate a measured result from an untested explanation. Stop when the claim is supported at its stated scope or the remaining evidence gap is explicit.
Adapted from Lauren Tan's pstack benchmark-checklist, under the MIT license.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Read public X/Twitter post URLs as structured evidence through the ADHX API. Use for relevant user-provided or research-discovered x.com, twitter.com, or adhx.com links. ADHX does not search X, and long-form Article content may be incomplete.
The English summary is being prepared. Showing the original description.
Trace what an actual code change could break beyond its diff when interfaces, serialized data, database schemas, configuration, caches, lifecycle ordering, or cross-language consumers are involved. Use for explicit impact analysis; not local renames, prose edits, ordinary dependency bumps, or generic architecture discussion.
The English summary is being prepared. Showing the original description.
Shared vocabulary for designing deep modules, interfaces, seams, adapters, leverage, and locality. Use when designing or reshaping module boundaries, making code more testable, or evaluating interface depth.
The English summary is being prepared. Showing the original description.
Plan or implement retirement of a system, API, feature, persisted configuration, or database shape. Use for compatibility cutovers, explicit deprecation review, or an explicit unreleased replacement decision, including determining whether consumers or data exist; not ordinary dependency bumps, local renames, prose edits, or generic architecture discussion.
The English summary is being prepared. Showing the original description.
Disciplined diagnosis loop for hard bugs, regressions, flaky failures, and performance problems with unclear cause. Use for root-cause debugging after a concrete symptom exists; do not use for routine implementation or speculative cleanup.
The English summary is being prepared. Showing the original description.
Route requests for current library, framework, SDK, API, CLI, or cloud-service documentation through available documentation tools and primary sources.
The English summary is being prepared. Showing the original description.