ln-503-regression-checker
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 and ln-502)
- Code quality check passed
Workflow (concise)
- Auto-discover framework and test locations from repo config/files.
- Read
docs/project/runbook.md— get exact test commands, Docker setup, environment variables. Use commands from runbook, NOT guessed commands. - Build appropriate test command; run with timeout (~5m); capture stdout/stderr.
- Parse results: passed/failed counts; key failing tests.
- Output verdict JSON (PASS or FAIL + failures list) and add Linear comment.
More from levnikolaevich/claude-code-skills
ln-624-code-quality-auditor
Checks cyclomatic complexity, nesting, long methods, god classes, O(n2), N+1 queries, constants management. Use when auditing code quality.
413ln-620-codebase-auditor
Use when auditing the codebase through the evaluation platform with mandatory research, coordinated domain audit workers, and structured summaries.
376ln-100-documents-pipeline
Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.
371ln-626-dead-code-auditor
Checks unreachable code, unused imports/variables/functions, commented-out code, unsupported patterns. Use when auditing dead code.
354ln-782-test-runner
Executes all test suites and reports results with coverage. Use when verifying that test infrastructure works after bootstrap.
343ln-775-api-docs-generator
Configures Swagger/OpenAPI documentation for backend APIs. Use when adding interactive API docs to a project.
339