القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
This skill should be used when the user asks "mira status", "show status", "how is mira doing", "system status", "index stats", "show mira stats", or wants a quick overview of Mira's index, storage, and active goals.
This skill should be used when the user asks "show my goals", "what should I work on", "update goal progress", "create a goal", "add milestone", "complete milestone", "track progress", "manage milestones", or wants to track work across multiple sessions.
This skill should be used when the user asks "what did you learn", "show insights", "any patterns noticed", "what should I know", "background analysis", "what patterns", or wants to see Mira's background analysis and predictions.
This skill should be used when the user asks "what were we working on", "session recap", "remind me of context", "catch me up", "restore context", "previous session", or starts a new session needing prior context.
Reference for all Mira MCP tool signatures, parameters, and workflows.
This skill should be used when the user asks "find code that does X", "search for X", "where is X implemented", "what handles X", "find the X logic", "search by meaning", "semantic search", or needs to find code by concept or intent rather than exact text matching.
| name | diff |
| description | 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. |
| argument-hint | [from_ref] [to_ref] |
Analyze git changes semantically with classification, impact analysis, and risk assessment.
Arguments: $ARGUMENTS
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)Use the mcp__mira__diff tool:
diff(from_ref="...", to_ref="...", include_impact=true)
Present results in sections:
/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
## 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)