🎯

ln-502-regression-checker

🎯Skill

from levnikolaevich/claude-code-skills

What it does

Automatically detects and runs the full test suite to identify potential regressions, parsing results without modifying project status.

📦

Part of

levnikolaevich/claude-code-skills(85 items)

ln-502-regression-checker

Installation

Claude CodeAdd plugin in Claude Code

/plugin add levnikolaevich/claude-code-skills

git cloneClone repository

git clone https://github.com/levnikolaevich/claude-code-skills.git ~/.claude/skills

📖 Extracted from docs: levnikolaevich/claude-code-skills

Need more details? View full documentation on GitHub →

12Installs

AddedFeb 4, 2026

View on GitHub Back to Skills

Skill Details

SKILL.md

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

Overview

# 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-500-story-quality-gate Pass 1 (after ln-501)
Code quality check passed
Before test planning pipeline (ln-510)

Workflow (concise)

1) Auto-discover framework and test locations from repo config/files.

2) Read docs/project/runbook.md — get exact test commands, Docker setup, environment variables. Use commands from runbook, NOT guessed commands.

3) Build appropriate test command; run with timeout (~5m); 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: ../ln-510-test-planner/references/risk_based_testing_guide.md

---

Version: 3.1.0 (Added mandatory runbook.md reading before test execution)

Last Updated: 2026-01-09

More from this repository10

🏪

levnikolaevich-claude-code-skills🏪Marketplace

Official marketplace for Agile Linear Workflow plugin - complete end-to-end automation for software development teams using Linear. Includes 7XX Project Bootstrap series for technology-agnostic project migration.

🎯

ln-140-test-docs-creator🎯Skill

Generates comprehensive test documentation with testing strategy and test organization structure for software projects.

🎯

ln-110-project-docs-coordinator🎯Skill

Coordinates project documentation by gathering context once, detecting project type, and delegating document creation to 5 specialized workers.

🎯

ln-114-frontend-docs-creator🎯Skill

Generates design guidelines documentation for frontend projects with WCAG 2.1 compliance when a frontend framework is detected.

🎯

ln-113-backend-docs-creator🎯Skill

Generates backend documentation files (API spec and database schema) automatically when backend or database technologies are detected in a project.

🎯

ln-610-code-comments-auditor🎯Skill

Audits code comments and docstrings across 6 quality categories, generating a comprehensive compliance score and actionable recommendations for improvement.

🎯

ln-115-devops-docs-creator🎯Skill

Generates a comprehensive runbook.md for DevOps setup, dynamically tailored to project's Docker configuration and deployment specifics.

🎯

ln-772-error-handler-setup🎯Skill

Configures global exception handling middleware for .NET and Python backend applications with standardized error responses.

🎯

ln-120-reference-docs-creator🎯Skill

Generates reference documentation structure and smart documents for project tech stack, creating only justified architectural decision records and guides.

🎯

ln-625-dependencies-auditor🎯Skill

Audits dependencies for outdated packages, unused imports, unnecessary libraries, and custom implementations, providing actionable recommendations.