groove-work-review
Evaluate output, identify lessons, decide accept/rework. Use after implementation.
What this skill does
# groove-work-review ## Outcome The artifact is reviewed for correctness, quality, and fit to plan. Lessons are identified for the compound stage. A clear accept/rework decision is made with rationale. Review notes are captured in the task body. ## Acceptance Criteria - Artifact is evaluated against the plan and acceptance criteria - Specific gaps or issues are identified (not vague "needs improvement") - Accept or rework decision is stated with rationale - Lessons are noted for `/groove-work-compound` - Review notes appended to stage task body - Stage task created in backend: `YYYY-MM-DD, Review` ## Steps 1. **Branch-diff analysis**: determine the base branch (default: `main`; override with `base:` arg if provided). Run: - `git log --oneline <base>...HEAD` — list commits on this branch - `git diff <base>...HEAD --stat` — summarise changed files - `git diff <base>...HEAD` — full diff (use as review input) Use this diff as the primary artifact to evaluate. If no commits beyond base exist, review working-tree changes instead. 2. **Evaluate against plan and acceptance criteria** — read the plan from the task body or spec file if available. 3. **Categorise findings** (use these exact labels): - **Fix Now**: trivial issues — fix immediately before accepting - **Needs Spec**: important gaps requiring planning — create a spec - **Create Issues**: large effort or nice-to-have — track as tasks 4. **State accept or rework decision** with rationale. 5. **Note lessons** for `/groove-work-compound`. 6. **Append review notes** to the task body. 7. **Create stage task** via `/groove-utilities-task-create` if `tasks.backend != none` (title `YYYY-MM-DD, Review`). ## Constraints - Read `tasks.backend` from `.groove/index.md` to determine backend - Be thorough — 80% of compound loop value is here and in plan - If rework: note specific gaps and link back to which plan step was missed or unclear - If accept: still note what worked well and what could be improved next time - Do not skip review even for small changes — capture something
Related in Code Review
gstack
IncludedFast 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)
startup-due-diligence
IncludedLegal 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.
interview-master
IncludedThis 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.
fix-issue
IncludedFixes 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.
sf-apex
IncludedGenerates 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.
swift-development
IncludedComprehensive 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.