regression-triage

regression-triage is a skill for Claude Code from loopdive/js2. It costs 72 tokens per session (2,010 once invoked), scanned A, original, Apache-2.0.

A process for sorting many test262 failures, where test262 is a standard JavaScript language test suite, after a continuous-integration run.

In plain words
What is it for?
It helps download merged test reports, group failures by paths and error patterns, inspect samples, and choose fixes or follow-up work.
Why use it?
It separates real regressions from false alarms and known limitations when a large test run reports mixed results.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node scripts/fetch-baseline-jsonl.mjs.

Good fit It helps download merged test reports, group failures by paths and error patterns, inspect samples, and choose fixes or follow-up work.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/loopdive/js2
agentmods
npx agentmods add skills/loopdive/js2/regression-triage

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for regression-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/loopdive/js2/regression-triage/github.svg)](https://agentmods.dev/skills/loopdive/js2/regression-triage)
Your own site
<a href="https://agentmods.dev/skills/loopdive/js2/regression-triage"><img src="https://agentmods.dev/badge/skills/loopdive/js2/regression-triage/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for regression-triage

Your own site · 80×15
<a href="https://agentmods.dev/skills/loopdive/js2/regression-triage"><img src="https://agentmods.dev/badge/skills/loopdive/js2/regression-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,010 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium MCP Rug Pull · line 73
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00072 $0.02010
Opus 5.5 $0.00029 $0.00804
Sonnet 5.5 $0.00014 $0.00402
Haiku 4.5 $0.00007 $0.00201

Measured 1mo ago against content hash 5eeb385a282d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

regression-triage scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/regression-triage/SKILL.md · 187 lines

How it starts

The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Regression Triage

Given the regression artifact from a sharded test262 CI run, bucket the regressions by path prefix and error message pattern, sample each concentrated bucket to determine root cause, and classify as false positive, known gap, or real regression with a fix path.

When to use

  • After a sharded run fails with N regressions but the net delta is positive (e.g. "+479 pass with 80 regressions")
  • When you need to decide which regressions block a baseline commit vs which get filed as follow-ups
  • When multiple merges could have introduced overlapping fails and you need to untangle them

Distinct from:

  • handle-regression — fixing a single specific regression
  • analyze-regression — diffing two JSONL result files (that's step 1 here)

Step 1: Download the merged report artifact

mkdir -p output/regressions-$(date +%s)
gh run download <RUN_ID> -n test262-merged-report -D output/regressions-<TIMESTAMP>

Files: test262-report-merged.json, test262-regressions.txt, test262-results-merged.jsonl.

test262-regressions.txt only has summary stats. Extract the actual regression LIST by diffing the merged jsonl against the current baseline:

Step 2: Compute the regression list

The baseline JSONL is fetched on demand from loopdive/js2wasm-baselines (#1528). Make sure the local cache is populated before diffing:

node scripts/fetch-baseline-jsonl.mjs
import json
base = {}
with open('.test262-cache/test262-current.jsonl') as f:
    for line in f:
        try:
            d = json.loads(line)
            base[d['file']] = d['status']
        except: pass

new = {}
new_details = {}
with open('/tmp/regressions-<TS>/test262-results-merged.jsonl') as f:
    for line in f:
        try:
            d = json.loads(line)
            new[d['file']] = d['status']
            new_details[d['file']] = d
        except: pass

regressions = [(f, new.get(f, 'missing'), new_details.get(f, {}))
               for f, s in base.items()
               if s == 'pass' and new.get(f, 'missing') != 'pass']
print(f"Total: {len(regressions)}")

Read the full file on GitHub · 187 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 187 lines · 72 tokens per session scan A 5eeb385a282d

Subscribe to this mod's changes

regression-triage is a skill published in the GitHub repository loopdive/js2 (67 stars, last pushed today), licensed Apache-2.0. It adds 72 tokens to every session and 2,010 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

migrate-oxlint

Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.

oxc-project/oxc · 44 tokens

insta-snapshots

Review and update Oxc Insta snapshots non-interactively after expected output changes or snapshot test failures.

oxc-project/oxc · 25 tokens

fixing-flaky-tests

Guides an agent through reproducing, root-causing, fixing, and validating flaky tests in the PostHog monorepo. Use when a test fails intermittently in CI but passes on rerun or locally, when hogli ci:insights or the debugging-ci-failures skill classifies a failure as a flaky test, when given a GitHub Actions URL for a…

PostHog/posthog · 220 tokens

test-electron-app

Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…

PostHog/posthog · 112 tokens

extending-hobby-smoke-tests

Design, extend, review, or debug PostHog Hobby end-to-end smoke tests in bin/hobby-ci.py and .github/workflows/ci-hobby.yml. Use when adding an ingestion round trip, deciding whether a product belongs in Hobby CI, changing the CI Hobby service topology or API-key scopes, or diagnosing a smoke test that captures data…

PostHog/posthog · 83 tokens

extending-personhog-test-harness

When and how to add scenarios, chaos events, and invariants to the personhog e2e test harness (rust/personhog-test-harness). Use after fixing a bug or regression in the personhog leader path (leader, router, writer, replica, coordination protocol) so the fix gets a permanent regression scenario; when adding a new…

PostHog/posthog · 134 tokens