ln-513-regression-checker

Solid

Runs existing test suite to catch regressions after implementation changes. Use when Story needs regression verification. No status changes.

AI & Automation 479 stars 67 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
89
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

> **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. If `shared/` is missing, fetch files via WebFetch from `https://raw.githubusercontent.com/levnikolaevich/claude-code-skills/master/skills/{path}`. # Regression Checker **Type:** L3 Worker **Category:** 5XX Quality Runs the existing test suite to ensure no regressions after implementation changes. ## Inputs | Input | Required | Source | Description | |-------|----------|--------|-------------| | `storyId` | Yes | args, git branch, kanban, user | Story to process | **Resolution:** Story Resolution Chain. **Status filter:** To Review ## Purpose & Scope - Detect test framework (pytest/jest/vitest/go test/etc.) and test dirs. - Execute full suite; capture stdout/stderr for Story quality gate. - Return PASS/FAIL with counts/log excerpts; never modifies Linear or kanban. - Preserve full stdout/stderr output for downstream log analysis. ## When to Use - After code quality checks pass - Code quality check passed ## Workflow ### Phase 0: Resolve Inputs **MANDATORY READ:** Load `shared/references/input_resolution_pattern.md`, `shared/references/ci_tool_detection.md` 1. **Resolve storyId:** Run Story Resolution Chain per guide (status filter: [To Review]). ### Phase 1: Execute Tests **MANDATORY READ:** Load `shared/references/output_normalization.md` Read target project files if they exist: `d...

Details

Author
levnikolaevich
Repository
levnikolaevich/claude-code-skills
Created
7 months ago
Last Updated
yesterday
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

ln-511-code-quality-checker

Checks DRY/KISS/YAGNI/architecture compliance with quantitative Code Quality Score. Use when implementation tasks are Done and need quality scoring.

479 Updated yesterday
levnikolaevich
AI & Automation Solid

ln-522-manual-tester

Performs manual testing of Story AC via executable bash scripts in tests/manual/. Use when Story implementation needs hands-on AC verification.

479 Updated yesterday
levnikolaevich
Testing & QA Listed

regression-testing

Execute regression test suites via CI/CD, analyze results, classify failures, and produce GO/NO-GO release decisions. Use when running regression, smoke, or sanity suites through GitHub Actions, monitoring workflow runs, downloading Allure or Playwright artifacts, classifying failures (REGRESSION vs FLAKY vs KNOWN vs ENVIRONMENT vs NEW TEST), computing pass-rate and trend metrics, deciding release readiness, generating executive quality reports, or creating regression issues. Triggers on: run regression, trigger test workflow, analyze test results, quality report, GO/NO-GO decision, release readiness, flaky tests, Allure report, smoke suite, pass rate, nightly test failure, stage 6. Do NOT use for writing new regression tests (that belongs to test-automation) or for manual fix verification (that belongs to sprint-testing).

11 Updated today
upex-galaxy
AI & Automation Solid

ln-510-quality-coordinator

Coordinates code quality checks: metrics, cleanup, agent review, regression, log analysis. Use when Story needs quality_verdict with aggregated results.

479 Updated yesterday
levnikolaevich
AI & Automation Solid

ln-523-auto-test-planner

Plans automated tests (E2E/Integration/Unit) using Risk-Based Testing after manual testing. Use when Story needs a test task with prioritized scenarios.

479 Updated yesterday
levnikolaevich