with one click
metrics-drilldown
metrics-drilldown contains 26 collected skills from grafana, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Skill for the App area of metrics-drilldown. 24 symbols across 16 files.
Skill for the AppDataTrail area of metrics-drilldown. 28 symbols across 17 files.
Skill for the Bookmarks area of metrics-drilldown. 14 symbols across 11 files.
Skill for the Breakdown area of metrics-drilldown. 15 symbols across 9 files.
Skill for the Components area of metrics-drilldown. 25 symbols across 15 files.
Skill for the Extensions area of metrics-drilldown. 17 symbols across 8 files.
Skill for the Fetchers area of metrics-drilldown. 11 symbols across 3 files.
Skill for the Labels area of metrics-drilldown. 12 symbols across 4 files.
Skill for the MetricDatasourceHelper area of metrics-drilldown. 22 symbols across 7 files.
Skill for the MetricLabelValuesList area of metrics-drilldown. 28 symbols across 12 files.
Skill for the Metrics-variables area of metrics-drilldown. 35 symbols across 15 files.
Skill for the MetricScene area of metrics-drilldown. 15 symbols across 9 files.
Skill for the MetricsFilterSection area of metrics-drilldown. 14 symbols across 4 files.
Skill for the MetricsGroupByList area of metrics-drilldown. 16 symbols across 9 files.
Skill for the QuickSearch area of metrics-drilldown. 25 symbols across 17 files.
Skill for the RelatedLogs area of metrics-drilldown. 12 symbols across 2 files.
Skill for the RelatedMetrics area of metrics-drilldown. 13 symbols across 11 files.
Skill for the SavedQueries area of metrics-drilldown. 12 symbols across 3 files.
Skill for the Stat area of metrics-drilldown. 12 symbols across 8 files.
Skill for the Timeseries area of metrics-drilldown. 13 symbols across 8 files.
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"