review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
What this skill does
# Review Delta Perform a focused, token-efficient code review of only the changed code and its blast radius. **Token optimization:** Before starting, call `get_docs_section_tool(section_name="review-delta")` for the optimized workflow. Use ONLY changed nodes + 2-hop neighbors in context. ## Steps 1. **Ensure the graph is current** by calling `build_or_update_graph_tool()` (incremental update). 2. **Get review context** by calling `get_review_context_tool()`. This returns: - Changed files (auto-detected from git diff) - Impacted nodes and files (blast radius) - Source code snippets for changed areas - Review guidance (test coverage gaps, wide impact warnings, inheritance concerns) 3. **Analyze the blast radius** by reviewing the `impacted_nodes` and `impacted_files` in the context. Focus on: - Functions whose callers changed (may need signature/behavior verification) - Classes with inheritance changes (Liskov substitution concerns) - Files with many dependents (high-risk changes) 4. **Perform the review** using the context. For each changed file: - Review the source snippet for correctness, style, and potential bugs - Check if impacted callers/dependents need updates - Verify test coverage using `query_graph_tool(pattern="tests_for", target=<function_name>)` - Flag any untested changed functions 5. **Report findings** in a structured format: - **Summary**: One-line overview of the changes - **Risk level**: Low / Medium / High (based on blast radius) - **Issues found**: Bugs, style issues, missing tests - **Blast radius**: List of impacted files/functions - **Recommendations**: Actionable suggestions ## Advantages Over Full-Repo Review - Only sends changed + impacted code to the model (5-10x fewer tokens) - Automatically identifies blast radius without manual file searching - Provides structural context (who calls what, inheritance chains) - Flags untested functions automatically
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.