final-review

Included with Lifetime

$97 forever

Final quality review producing a human-readable report

Code Review

What this skill does


# Final Review

Produce a final human-readable review report after all fixes have been applied. This report is for a human reviewer — concise, clear, and focused on whether the story is ready for merge.

## Input

`$ARGUMENTS` is the path to a story file.

## Steps

### 1. Read Context

Derive `story-slug` from the story filename. Read:

- The story file at `$ARGUMENTS` — for acceptance criteria
- `docs/reviews/{story-slug}/02-review.md` — previous review findings
- `docs/reviews/{story-slug}/03-fix.md` — what was fixed (if it exists)

### 2. Learn the Project

Discover the project's test commands by exploring project configuration files. Look at existing source files to understand the code style and conventions.

### 3. Verify Previous Findings Resolved

For each Critical and Warning finding from the previous review, check the specific file and line referenced. Confirm the fix was applied correctly.

### 4. Fresh Review

Run `git diff --name-only HEAD` and `git status --short` to find all changed files. Read every changed file.

Do a holistic review focused on:

- Do all the pieces fit together cohesively?
- Were any new issues introduced by the fixes?
- Is every acceptance criterion covered by a passing test?
- Would a human reviewer find anything surprising or concerning?

### 5. Run Tests

Run the project's test command. Confirm all tests pass.

### 6. Write Final Report

Write to `docs/reviews/{story-slug}/04-final-review.md`:

```markdown
# Final Review

**Story:** {story file path}
**Date:** {ISO date}
**Verdict:** {READY FOR MERGE | NEEDS ATTENTION}

## What Was Built

{2-3 sentence summary suitable for a PR description}

## Acceptance Criteria

| Criterion        | Status    | Test             |
| ---------------- | --------- | ---------------- |
| {criterion text} | PASS/FAIL | {test reference} |

## Previous Review

- **Critical findings:** {N} found, {N} resolved
- **Warnings:** {N} found, {N} resolved

## Remaining Concerns

{List any issues that still need attention, or "None"}

## Files Changed

- `path/to/file` — {one-line description}

## Test Results

{Summary: N tests passed, 0 failed}
```

### 7. Output Verdict

After writing the report, output:

- The verdict (READY FOR MERGE or NEEDS ATTENTION)
- The report file path
- A one-line summary

## Rules

- The report is for humans — be concise, not exhaustive.
- If any acceptance criterion lacks a test, mark it FAIL.
- If any Critical finding from the previous review was not resolved, verdict is NEEDS ATTENTION.
- Be honest about the verdict — READY FOR MERGE means you'd be comfortable merging this.

Files: 1

Size: 2.7 KB

Complexity: 5/100

Category: Code Review

Source: https://github.com/psousa50/claude-plugins/tree/main/plugins/develop/skills/final-review

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