plan-quality

Included with Lifetime

$97 forever

Code quality review of a plan file. Checks proposed changes against project code-quality criteria; annotates violations.

Code Review

What this skill does


# Code Quality Review

Review a plan file against code-quality criteria. Annotate where proposed implementations would violate them.

Plan file: **$ARGUMENTS**

This skill performs a specialized `plan-cycle-annotate` pass. It only adds notes; it does not run `plan-cycle-review` or `plan-cycle-finalize`.

## Step 1: Load criteria

Project root = `${CLAUDE_PROJECT_DIR}` if set, else `git rev-parse --show-toplevel`, else cwd (warn `"Using cwd as project root: <path>"`).

If `<project-root>/code-quality.md` exists: load it, print `"Using project criteria from <path>."` Otherwise load `${CLAUDE_SKILL_DIR}/code-quality.md` (default, 9 shipped criteria) and print:

> Using default code-quality criteria (9 shipped rules). To customize, create `<project-root>/code-quality.md` (start by copying `${CLAUDE_SKILL_DIR}/code-quality.md`).

The skill **never** creates, copies, or modifies files in the project root. If the loaded file is empty or has no `###` headings, stop and tell the user to add criteria using `### N. Name` headings.

## Step 2: Analyze and annotate

For each proposed change (code snippets, interfaces, signatures), check against EACH criterion. Focus on what's explicit — don't speculate about details left open.

For each violation, add an annotation below the relevant section. **Format:** defined in ops file `plan-cycle-annotate` section. Use `[quality: <criterion>]` prefix: `> **NOTE**: [quality: criterion-name] explanation + shape that would pass`. Cite criterion by name as in `###` heading. Be constructive.

## Threshold

If you find more than 15 violations, stop annotating individual items. Write a summary at the top of "Detailed Changes":

> **NOTE**: [quality] This plan has significant quality issues (N found across M criteria). Consider revisiting. Top criteria: [list top 3-4].

At the end, report: criteria checked, violations found, criteria triggered most.

Files: 2

Size: 7.4 KB

Complexity: 16/100

Category: Code Review

Source: https://github.com/elmisi/claude-code-automation/tree/main/plugins/plan-cycle/skills/plan-quality

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