verify-no-regressions

Included with Lifetime

$97 forever

Verify no behavioral regressions after implementation. Spawns parallel sonnet subagents for semantic diff review + test execution. Use when: user says "verify no regressions", "check for regressions", "make sure nothing broke".

Code Review

What this skill does


# Verify No Regressions

Usage: `/verify-no-regressions [count] [base-branch]` (defaults: 1 main)

## Work state

- Working tree: !`git status --short 2>/dev/null || echo "(not a git repo)"`
- Commits ahead of base: !`set -- $ARGUMENTS; git log --oneline "${2:-main}"...HEAD 2>/dev/null || echo "(none or invalid base)"`
- Committed diff: !`set -- $ARGUMENTS; git diff --stat "${2:-main}"...HEAD 2>/dev/null`
- Staged diff: !`git diff --cached --stat 2>/dev/null`
- Unstaged diff: !`git diff --stat 2>/dev/null`
- Test scripts: !`cat package.json 2>/dev/null | jq -r '.scripts | to_entries[] | select(.key | test("test";"i")) | "\(.key): \(.value)"' 2>/dev/null || echo "(no package.json)"`

## Instructions

Read the work state above to determine what happened:
- **Committed**: commits ahead of base, clean working tree → review with `git diff base...HEAD`
- **Staged**: files in staging → review with `git diff --cached`
- **Unstaged/untracked**: modified or new files → review working tree files directly
- **Mixed**: combination of the above → review all layers

If nothing changed anywhere, report that and stop.

Spawn **sonnet** subagents in a **single message**. Tell each agent which diff commands to use based on the work state.

1. **Semantic reviewers** -- split changed files across `$0` agent(s) (default: 1). Each agent:
   - Reads the diff (using the appropriate command for the work state) and current file contents
   - Classifies each change as INTENTIONAL, RISKY (could break callers), or REGRESSION
   - Reports verdict: PASS / NEEDS_REVIEW / FAIL

2. **Test runner** (skip if no test infrastructure) -- one additional agent that runs the test suite and reports PASS / FAIL.

After all agents complete, synthesize a single report with overall verdict.

Files: 1

Size: 2.1 KB

Complexity: 11/100

Category: Code Review

Source: https://github.com/bengous/claude-code-plugins/tree/main/claude-meta-tools/skills/verify-no-regressions

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts