code-review
Review code against project rules. Use when reviewing code quality or ensuring compliance with conventions.
What this skill does
## Context
- Rule files: !`find .claude/rules -name "*.md" -type f ! -path ".claude/rules/git/*"`
- Git status: !`git status --porcelain`
- Current branch: !`git branch --show-current`
- Branch diff vs master: !`git diff --name-only master...HEAD 2>/dev/null || echo ""`
## Your task
Check code against ALL rule files listed above. Launch ONE agent PER rule file, in PARALLEL.
### Determine what to check
1. If file with line range provided (e.g., `file.php:10-50`): check only those lines
2. If file path provided (e.g., `file.php`): check the entire file
3. If no arguments: use git status and branch diff above to find changed files
4. If no changes found: use AskUserQuestion to ask what to check
### For each rule file, spawn a Task agent
Use `subagent_type: Explore` with prompt:
```
Check this code against the rule.
RULE: {rule_file_path}
RULE CONTENT:
{read the rule file content}
FILES TO CHECK:
{list of files, filtered by rule's paths: frontmatter if present}
Report violations as:
- file:line - violation description
Code: `violating code`
Fix: `correct code`
If no violations, report: PASS
```
### Verify completeness
After spawning agents, verify:
1. Count the rule files listed in Context above
2. Count the agents you spawned
3. If counts don't match, identify which rules were missed and spawn agents for them
### Summarize results
After all agents complete, output:
- Rules checked (count) / Total rules (count)
- Rules passed (count)
- Violations found per rule with file:line and fix suggestionsRelated 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.