diff
This skill should be used when the user asks "analyze my changes", "what did I change", "review my diff", "impact of changes", "show changes", "git analysis", or wants semantic analysis of code changes.
What this skill does
# Semantic Diff Analysis Analyze git changes semantically with classification, impact analysis, and risk assessment. **Arguments:** $ARGUMENTS ## Instructions 1. Parse optional arguments: - `--from REF` → Starting git ref (default: HEAD~1 or staged changes) - `--to REF` → Ending git ref (default: HEAD) - `--no-impact` → Skip impact analysis (faster) 2. Use the `mcp__mira__diff` tool: ``` diff(from_ref="...", to_ref="...", include_impact=true) ``` 3. Present results in sections: ### Change Classification - **NewFunction**: Entirely new functions/methods - **ModifiedFunction**: Changed existing functions - **DeletedFunction**: Removed functions - **NewFile**: New files added - **Refactored**: Structural changes without behavior change ### Impact Analysis - What callers are affected by these changes - Which modules depend on modified code - Potential ripple effects ### Risk Assessment - **Breaking changes**: API signature changes, removed exports - **Security relevance**: Auth, input validation, crypto changes - **Test coverage**: Are changes covered by tests? ## Examples ``` /mira:diff → Analyzes staged/working changes vs HEAD /mira:diff --from main → Analyzes current branch vs main /mira:diff --from v1.0 --to v1.1 → Analyzes changes between tags /mira:diff --no-impact → Quick classification without call graph analysis ``` ## Example Output ``` ## Semantic Diff Analysis ### Changes (5 files, +142 -38 lines) **New Functions:** - `validate_token()` in src/auth.rs:45 **Modified Functions:** - `handle_login()` in src/auth.rs:23 (added rate limiting) - `create_session()` in src/session.rs:67 (changed return type) ### Impact Analysis - `handle_login()` is called by 3 endpoints - `create_session()` change affects 12 callers ### Risk Assessment [WARNING] **Breaking**: `create_session()` return type changed [SECURITY] **Security**: Rate limiting added (positive) ```
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.