code-review
Generic code review that auto-detects tech stack and delegates to appropriate framework-specific orchestrator
What this skill does
# Code Review
Generic code review command that detects your project's tech stack and delegates to the appropriate framework-specific review orchestrator.
## Config
```
TECH_STACK = config_read("tech_stack", "generic")
```
```bash
DEFAULT_BRANCH=$(git remote show origin | grep 'HEAD branch' | awk '{print $NF}')
```
## Arguments
<input_arguments> $ARGUMENTS </input_arguments>
**Scope modes:**
- `#123` or GitHub URL → PR changes
- (no args) → unstaged changes (working directory)
- `--staged` → staged changes only
- `--branch` → current branch vs default branch
- `path/to/file ...` → specific files
## Step 1: Detect Tech Stack
Use "Tech stack" from Context above. If empty, auto-detect from project files:
### Auto-Detection Fallback
If not configured in `.agents.yml`, detect from project files:
| Detection | Tech Stack |
|-----------|------------|
| `Gemfile` exists | `rails` |
| `pyproject.toml` or `requirements.txt` exists | `python` |
| `package.json` exists (no Gemfile) | `javascript` |
| None of the above | `generic` |
```bash
# Detection commands
[ -f Gemfile ] && echo "rails"
[ -f pyproject.toml ] || [ -f requirements.txt ] && echo "python"
[ -f package.json ] && echo "javascript"
```
## Step 2: Gather Changed Files
Based on scope from arguments:
```bash
# Default (unstaged changes)
git diff --name-only --diff-filter=d
# Staged mode
git diff --cached --name-only --diff-filter=d
# Branch mode (use "Default branch" from Context)
git diff <default_branch>...HEAD --name-only --diff-filter=d
# PR mode
gh pr diff <PR_NUMBER> --name-only
```
## Step 3: Delegate to Framework Orchestrator
Based on detected tech stack, invoke the appropriate orchestrator agent via Task tool:
### Rails Projects
```
Task: majestic-rails:review/code-review-orchestrator
Prompt: "Review these Rails files. Scope: [scope mode]
Changed files:
[file list]"
```
### Python Projects
```
Task: majestic-python:review/code-review-orchestrator
Prompt: "Review these Python files. Scope: [scope mode]
Changed files:
[file list]"
```
### JavaScript Projects (Not Yet Supported)
```markdown
**Tech Stack:** JavaScript
JavaScript code review orchestrator is not yet available.
For now, you can run the generic simplicity reviewer:
`Task(subagent_type: "simplicity-reviewer") [files]`
Or configure `tech_stack: generic` in AGENTS.md to use generic reviewers.
```
### Generic Projects
For unknown or generic tech stacks, run minimal reviewers directly:
1. Load project topics (if configured)
2. **Run both reviewers in parallel:**
3. Synthesize output
```
# Run these tasks in parallel:
Task 1: majestic-engineer:review/simplicity-reviewer
Prompt: "Review these files for YAGNI violations, unnecessary complexity: [file list]"
```
## Step 4: Report Results
The orchestrator will return a synthesized report. Present it to the user with:
1. **Status** - BLOCKED / NEEDS CHANGES / APPROVED
2. **Summary** - Key findings by severity (P1/P2/P3)
3. **Details** - Full agent reports in collapsible sections
## Tech Stack Configuration
To explicitly set your tech stack (recommended for multi-language projects), add to `AGENTS.md`:
```markdown
## Project Configuration
tech_stack: rails # rails | python | javascript | generic
```
## Examples
```bash
# Review unstaged changes (auto-detect tech stack)
Skill("code-review")
# Review staged changes
Skill("code-review") --staged
# Review current branch vs main
Skill("code-review") --branch
# Review a PR
Skill("code-review") #123
# Review specific files
Skill("code-review") app/models/user.rb app/controllers/users_controller.rb
```
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.