How does it determine the test framework?

It auto-discovers the framework using the Command Registry in shared/references/ci_tool_detection.md and falls back to the runbook if needed.

Will regression-checker modify project status, Linear, or kanban?

No. It only reports PASS/FAIL with any failing tests and logs; it does not modify statuses, Linear, or create tasks.

What happens if the test run times out?

Each run is bounded by a 5-minute timeout per ci_tool_detection.md. On timeout, it reports FAIL with a timeout note and relevant logs.

ln-514-regression-checker

Scanned

npx machina-cli add skill levnikolaevich/claude-code-skills/ln-514-regression-checker --openclaw

Files (1)

SKILL.md

1.9 KB

Paths: File paths (shared/, references/, ../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.

Regression Checker

Runs the existing test suite to ensure no regressions after implementation changes.

Purpose & Scope

Detect test framework (pytest/jest/vitest/go test/etc.) and test dirs.
Execute full suite; capture results for Story quality gate.
Return PASS/FAIL with counts/log excerpts; never modifies Linear or kanban.

When to Use

Invoked by ln-510-quality-coordinator Phase 7
Code quality check passed

Workflow (concise)

Auto-discover test framework per shared/references/ci_tool_detection.md Command Registry (Test Frameworks section).
Read docs/project/runbook.md — get exact test commands, Docker setup, environment variables. Runbook commands take priority over auto-detection (per ci_tool_detection.md Discovery Hierarchy).
Build appropriate test command; run with timeout (5min per ci_tool_detection.md); capture stdout/stderr.
Parse results: passed/failed counts; key failing tests.
Output verdict JSON (PASS or FAIL + failures list) and add Linear comment.

Critical Rules

No selective test runs; run full suite.
Do not fix tests or change status; only report.
Language preservation in comment (EN/RU).

Definition of Done

Framework detected; command executed.
Results parsed; verdict produced with failing tests (if any).
Linear comment posted with summary.

Reference Files

Risk-based limits used downstream: ../shared/references/risk_based_testing_guide.md
CI tool detection: shared/references/ci_tool_detection.md

Version: 3.1.0 Last Updated: 2026-01-09

Source

git clone https://github.com/levnikolaevich/claude-code-skills/blob/master/ln-514-regression-checker/SKILL.mdView on GitHub

Overview

ln-514-regression-checker runs the existing test suite to detect regressions after code changes. It auto-detects the test framework (pytest, jest, go test, etc.) and reports a PASS or FAIL verdict with counts and key failing tests, without modifying project status or creating tasks.

How This Skill Works

The tool auto-discovers the test framework via the Command Registry, reads the documented runbook for exact test commands, builds the appropriate test command, and runs it with a 5-minute timeout. It then parses stdout/stderr to extract pass/fail counts and failing tests, outputs a verdict JSON (PASS or FAIL + failures list), and posts a Linear comment. No status updates or task creation occur.

When to Use It

After code changes to validate no regressions
During ln-510-quality-coordinator Phase 7
When you rely on docs runbook for exact test commands and environment setup
When you need a precise PASS/FAIL verdict with failing tests and logs
When you require a non-intrusive quality gate that won’t alter statuses or tasks

Quick Start

Step 1: Auto-discover test framework via shared/references/ci_tool_detection.md
Step 2: Read docs/project/runbook.md for exact commands and environment setup
Step 3: Build and run the full test command within 5 minutes, parse results, publish verdict and Linear comment

Best Practices

Ensure the test suite is up to date and locally runnable before invoking regression-checker
Let auto-detection determine the framework, but verify the runbook-specified commands if needed
Run the full, non-selective test suite—no skipping of tests
Capture and preserve stdout/stderr excerpts for any failures
Review the failing tests list and include a concise Linear comment summarizing results

Example Use Cases

Python project with pytest after feature addition returns PASS with summary counts
Frontend project using jest shows specific failing tests and error excerpts
Go microservice with go test reports FAIL and lists failing tests with logs
Cross-language repo uses ci_tool_detection to auto-detect frameworks and run the full suite
CI Phase 7 gates, regression-checker prints verdict without updating Linear or kanban

Frequently Asked Questions

Add this skill to your agents