fresh-eyes
Re-reads code you just wrote with fresh perspective to catch bugs, errors, and issues. Use after completing a feature, fixing a bug, or any code changes. Triggers on "review my code", "fresh eyes", "check for bugs", "did I miss anything", or "sanity check".
What this skill does
# Fresh Eyes Review Re-read all code you just wrote or modified with a fresh perspective. Look for obvious bugs, errors, problems, and confusion that are easy to miss when deep in implementation. ## When to Use - After completing a feature or fix - Before committing changes - When you feel like something might be off - After a long coding session ## Process ### 1. Identify Changed Code Find all files you modified in this session. If unclear, ask the user or check recent git changes: ```bash git diff --name-only HEAD~1 git diff --name-only --cached ``` ### 2. Re-read with Fresh Eyes Read each modified file completely. Pretend you've never seen this code before. Look for: **Logic errors** - Off-by-one errors - Inverted conditions - Missing null/undefined checks - Race conditions - Incorrect comparisons (== vs ===, > vs >=) **Obvious bugs** - Typos in variable names - Copy-paste errors - Forgotten return statements - Unused variables that should be used - Wrong function called **Missing pieces** - Error handling gaps - Edge cases not covered - Cleanup code missing (close connections, clear timeouts) - Validation missing at boundaries **Confusion risks** - Misleading variable names - Complex logic without comments - Inconsistent patterns within the file - Magic numbers without explanation ### 3. Fix Issues For each issue found: 1. Explain what's wrong in 1 sentence 2. Fix it immediately 3. Move to the next issue Don't ask for permission. Just fix obvious problems. ### 4. Report Summary After fixing, provide a brief summary: ``` ## Fresh Eyes Review Fixed 3 issues: - `api/users.ts:47` — Missing null check on user.profile - `api/users.ts:82` — Off-by-one in pagination (used > instead of >=) - `utils/format.ts:15` — Typo: `formattedDte` → `formattedDate` No other issues found. ``` If nothing found: ``` ## Fresh Eyes Review Reviewed 4 files. No issues found. ``` ## What NOT to Do - Don't refactor working code - Don't add features - Don't change style preferences - Don't optimize prematurely - Don't add comments to obvious code - Don't reorganize file structure Focus only on **bugs, errors, and problems**. If it works and isn't broken, leave it alone. ## Checklist Run through mentally for each file: - [ ] All variables initialized before use? - [ ] All functions return what they should? - [ ] All loops terminate correctly? - [ ] All conditions handle both branches? - [ ] All async operations awaited? - [ ] All errors caught or propagated? - [ ] All resources cleaned up? - [ ] All edge cases handled (empty, null, zero, negative)?
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.