uncommitted

Included with Lifetime

$97 forever

Critically review uncommitted git changes (staged + unstaged + untracked) before committing.

Code Review

What this skill does


# Context

- Branch: !`git branch --show-current 2>/dev/null || echo "(not a git repo)"`
- File status: !`git status --porcelain 2>/dev/null || echo "(not a git repo)"`
- Staged stats: !`git --no-pager diff --stat --cached 2>/dev/null || true`
- Unstaged stats: !`git --no-pager diff --stat 2>/dev/null || true`
- Recent commits: !`git --no-pager log --oneline -5 2>/dev/null || true`

# Task

Review uncommitted changes in the working tree.

- If `$ARGUMENTS` is provided, focus the review on those paths (treat it like a path or glob).
- Review **staged**, **unstaged**, and **untracked** files.
- Start with the stats above; then use `git diff` (and `git diff --cached`) to inspect the actual changes.

## Focus areas (prioritize actual problems)

- **Path accuracy**: Any moved/renamed files? Config/CI paths still correct?
- **Correctness**: Bugs, broken logic, missing edge handling at boundaries.
- **Completeness**: TODO/FIXME, commented-out code, debug artifacts, missing updates.
- **Consistency**: Lint/format violations, inconsistent naming, copy/paste duplication.
- **Security**: Secrets, unsafe shelling out, injection risks, overly-broad permissions.
- **Tests**: Are changes covered? Are tests meaningful (assert behavior, not implementation)?
- **Project rules**: If a `CLAUDE.md` exists, call out any violated constraints or needed updates.
- **Docs sync**: If behavior/config changed, note what docs need updating.

## Tests (ask first)

Detect likely test commands (from `package.json`, `Makefile`, common configs). **Do not run tests by default.**

- Propose the most likely test command(s).
- Ask the user whether to run them.
- If the user approves, run the chosen test command and report results.

## Output format

**Summary**
- 2-3 lines describing the changes and overall assessment

**Critical Issues**
- Only blocking problems that MUST be fixed (broken CI paths, missing files, failing logic)
- Include specific files and line numbers when possible

**Improvements (Should Address)**
- Non-blocking but important issues

**Suggested Tests**
- Command(s) to run and why

**Test Results** (only if tests were run)
- Command executed: [exact command]
- Pass/Fail status
- Any new failures introduced by changes

Be direct. Focus on actual issues, not hypothetical edge cases.

Files: 1

Size: 2.5 KB

Complexity: 10/100

Category: Code Review

Source: https://github.com/mrclrchtr/cc-marketplace/tree/main/plugins/review/skills/uncommitted

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