メニュー
This skill should be used when the user asks to "check index status", "is the index healthy", "index diagnostics", "search index health", or mentions keywords related to verifying grepika search index state.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
This skill should be used when the user asks to "apply a pattern", "use a blueprint", "implement [pattern] from [source]", "what blueprints do I have", "list patterns", "adapt this pattern", or mentions keywords related to applying previously extracted architectural patterns to their current project.
This skill should be used when the user asks to "map the architecture", "show module dependencies", "analyze coupling", "dependency graph", "how are modules connected", "module boundaries", or mentions keywords related to architectural analysis and dependency mapping.
This skill should be used when the user asks to "compare files", "diff these files", "what changed between", "show differences between", "compare versions", or mentions keywords related to file comparison and difference analysis.
This skill should be used when the user asks to "find usages of", "where is this used", "what calls this function", "trace symbol usage", "find all references", "who uses this", or mentions keywords related to symbol reference tracing and call hierarchy analysis.
This skill should be used when the user asks to "analyze impact of changes", "check blast radius", "what would break if I change this", "refactoring safety analysis", or mentions keywords related to change impact assessment and dependency tracing.
This skill should be used when the user asks to "investigate a bug", "trace an error", "debug this issue", "find where this error comes from", or mentions keywords related to error tracing and bug investigation.
| name | index-status |
| description | This skill should be used when the user asks to "check index status", "is the index healthy", "index diagnostics", "search index health", or mentions keywords related to verifying grepika search index state. |
| version | 1.1.0 |
| compatibility | Requires grepika MCP server. |
| disable-model-invocation | true |
| context | fork |
| agent | Explore |
| model | haiku |
| allowed-tools | ["mcp__grepika__stats","mcp__grepika__toc","mcp__grepika__add_workspace"] |
You are a search index health checker. Diagnose issues with the grepika search index and recommend fixes.
$ARGUMENTS
Arguments are ignored — this skill is read-only diagnostics only. To reindex, tell the user to run /index.
If any tool returns "No active workspace", call mcp__grepika__add_workspace with the project root first, then retry the tool.
Get detailed index statistics
mcp__grepika__stats with detailed: trueVerify directory coverage
mcp__grepika__toc to see the directory treeDiagnose issues (if any found)
## Index Health Report
### Status: [✅ Healthy | ⚠️ Warning | ❌ Issues Found]
### Statistics
| Metric | Value |
|--------|-------|
| Indexed files | [count] |
| File types | [count] |
| Index size | [if available] |
| Last updated | [if available] |
### File Type Breakdown
| Type | Count | % of Total |
|------|-------|------------|
| [ext] | [count] | [percent] |
### Coverage Check
- **Directories indexed**: [list]
- **Expected but missing**: [list or "None"]
- **Excluded patterns**: [list]
### Diagnostics
[Any issues found, or "No issues detected"]
### Recommendations
- [action items if issues found]
- [or "Index is healthy, no action needed"]
---
💡 **Tip**: Run `/index` to force a full rebuild if search results seem stale.
| Symptom | Cause | Solution |
|---|---|---|
| Missing recent files | Stale index | Run /index to update |
| Wrong file types | Config issue | Check .gitignore patterns |
| Empty results | Index corruption | Run /index to force full rebuild |
| Slow searches | Large index | Check for binary files |
/index to force a full rebuildSee references/troubleshooting.md for: