reviewing

Included with Lifetime

$97 forever

Use when the final swarm phase completes. Run specialist review, artifact verification, UAT, review beads, finishing checks, and handoff to compounding.

Code Review

What this skill does

# Reviewing

If `.khuym/onboarding.json` is missing or stale for the current repo, stop and invoke `khuym:using-khuym` before continuing.

Reviewing is the final automated quality gate after execution. It verifies that the completed feature is correct, safe, wired, and acceptable to the user before compounding begins.

## Required Inputs

- `history/<feature>/CONTEXT.md`
- `history/<feature>/approach.md`
- `.khuym/state.json`
- current git diff or merged branch range
- live bead graph for the feature epic

## Operating Contract

1. Dispatch specialist review agents with isolated context.
2. Convert each real review issue into a review bead.
3. Stop on P1 findings until the user acknowledges the gate.
4. Verify every promised artifact at the EXISTS, SUBSTANTIVE, and WIRED levels.
5. Walk the user through UAT items from locked decisions.
6. Finish by checking all beads, running project quality gates, closing the epic, and preparing compounding.

Load `references/reviewing-reference.md` for the agent roster, severity rules, artifact verification, UAT flow, review bead schema, and finishing checklist.

## Hard Gates

- P1 review beads block merge. Never continue past P1 without user acknowledgment.
- Artifact verification is mandatory; task closure is not proof that the feature works.
- UAT failures are never logged as passes. Skips need a reason in `.khuym/state.json`.
- P2/P3 review beads must use non-blocking traceability, not current-epic child links.
- Agent 5, `learnings-synthesizer`, always runs after agents 1-4.

## Handoff

After finishing:

```json
{
"active_skill": "reviewing",
"phase": "reviewing-complete",
"epic_id": "<id>",
"summary": "Review complete. Ready to run compounding.",
"next_action": "Invoke khuym:compounding.",
"focus": "compounding",
"blockers": []
}
```

Tell the user: `Feature complete. Epic <id> closed. Invoke khuym:compounding skill.`

## Reference Files

| File | When to Load |
|---|---|
| `references/reviewing-reference.md` | Review flow, specialist roster, review bead schema |

Files: 2

Size: 6.1 KB

Complexity: 23/100

Category: Code Review

Source: https://github.com/hoangnb24/skills/tree/main/plugins/khuym/skills/reviewing

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