code-review-preferences
Use when reviewing code, PRs, or discussing code quality standards. Applies team coding standards and review methodology.
What this skill does
<essential_principles> ## Code Review Philosophy Reviews exist to: 1. **Catch bugs** before production 2. **Share knowledge** across the team 3. **Maintain consistency** in the codebase Reviews do NOT exist to: - Show off knowledge - Enforce personal style preferences - Block progress unnecessarily ## The 3-Pass Method ### Pass 1: Understand (don't comment yet) - What is this change trying to do? - What files are affected? - What's the scope? ### Pass 2: Correctness - Are there bugs? - Are edge cases handled? - Are there security issues? ### Pass 3: Improvements (max 5 comments) - Is it readable? - Is it maintainable? - Are there better patterns? ## Review Standards ### Must Check - [ ] Tests pass - [ ] No obvious bugs - [ ] Edge cases from PR description handled - [ ] No security vulnerabilities - [ ] No secrets in code ### Should Check - [ ] Code is readable - [ ] Functions are reasonably sized (<50 lines) - [ ] Names are clear and descriptive - [ ] Error messages are helpful ### Nice to Check - [ ] Performance considerations - [ ] Documentation updated - [ ] Consistent with existing patterns ## Feedback Style **DO:** - Ask questions: "What happens if X is null?" - Be specific: "Line 42: Consider using a guard clause" - Acknowledge good work: "Nice refactor here" - Limit comments: Max 5 per review **DON'T:** - Dictate: "You must do X" - Be vague: "This could be better" - Nitpick style: "I prefer single quotes" - Pile on: 20 comments is overwhelming </essential_principles> <intake> What would you like me to review? 1. **Format** - Paste the code/diff here - Reference a file with @filename - Describe the PR and I'll ask questions 2. **Context** - Bug fix - New feature - Refactor - Performance optimization - Other: ___ 3. **Specific concerns?** (Security, performance, breaking changes, etc.) **I'll wait for your answers before starting the review.** </intake>
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.