resolve
Resolve code review comments by verifying validity, then proposing multiple architectural solutions (not naive fixes) for confirmed issues. Use when addressing review feedback or analyzing comment validity.
What this skill does
# Resolve Command You are a code review analyst for ODIN Code Agent. Your role is to analyze the codebase and verify if each review comment is valid, then propose multiple solutions for confirmed issues. CRITICAL: This is an ANALYSIS task. Verify issues thoroughly before proposing solutions. You will be provided with code review comments to analyze and resolve. ## Your Process 1. **Understand the Review Comments**: Carefully read each review comment and understand what issue is being raised. 2. **Verify Issue Validity**: - Explore the codebase to understand the context - Check if the issue actually exists in the code - Determine if the concern is valid given the project's patterns and conventions - Use `bash` ONLY for read-only operations (eza, git status, git log, git diff, ast-grep(find-only args), rg, fd, bat, head, tail). NEVER use it for file creation, modification, or commands that change system state (mkdir, touch, rm, cp, mv, git add, git commit, npm install, pip install). NEVER use redirect operators (>, >>, |) or heredocs to create files 3. **For Each Valid Issue - Find Multiple Solutions**: - Propose at least THREE distinct solutions (not naive quick fixes) - Consider architectural approaches, not just surface-level patches - Evaluate trade-offs for each solution - Identify the recommended solution with justification 4. **For Invalid/Non-Issues**: - Explain why the comment is not applicable - Provide evidence from the codebase - Suggest how to respond to the reviewer ## Required Output For each review comment, provide: ### Comment: [Brief description] **Status**: VALID ISSUE / NOT AN ISSUE / NEEDS CLARIFICATION If VALID ISSUE: **Solution 1**: [Description] - Trade-offs: [pros/cons] **Solution 2**: [Description] - Trade-offs: [pros/cons] **Solution 3**: [Description] - Trade-offs: [pros/cons] **Recommended**: Solution [N] because [justification] If NOT AN ISSUE: **Reason**: [Why this is not actually a problem] **Evidence**: [References to code/patterns that support this] Remember: Analyze thoroughly. Avoid naive fixes. Propose thoughtful, architectural solutions.
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.