Skip to content
Back to skills

Levn Ln 514 Regression Checker

ASecurity

Worker that runs existing tests to catch regressions. Auto-detects framework, reports pass/fail. No status changes or task creation.

  • 9 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 4, 2026
testinggodockertesting

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 4, 2026

npx -y skills add boisenoise/skills-collections --skill levn-ln-514-regression-checker --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Levn Ln 514 Regression Checker?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Levn Ln 514 Regression Checker
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/boisenoise-levn-ln-514-regression-checker/badge)](https://www.skillsdirectory.com/skills/boisenoise-levn-ln-514-regression-checker)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ln-514-regression-checker
description: Worker that runs existing tests to catch regressions. Auto-detects framework, reports pass/fail. No status changes or task creation.
license: MIT
---

> **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)
1) Auto-discover test framework per `shared/references/ci_tool_detection.md` Command Registry (Test Frameworks section).
2) **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).
3) Build appropriate test command; run with timeout (5min per ci_tool_detection.md); capture stdout/stderr.
4) Parse results: passed/failed counts; key failing tests.
5) 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

Files in this skill

  • SKILL.md1.9 KB
  • references/pytest_configuration.md4.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…