Agent skill

ragsharp-query-code-graph

Query the ragsharp code graph for declarations, references, callers, callees, dependencies, and line-number evidence. Triggers: find usages, where defined, callers, callees, dependency path, project deps, type hierarchy, line numbers, evidence.

Stars 0
Forks 1

Install this agent skill to your Project

npx add-skill https://github.com/managedcode/RagSharp/tree/main/assets/skill-templates/query-code-graph

SKILL.md

Steps

  1. Run ragsharp graph query --type symbols --db .ragsharp/graph/index.db --limit 50 --symbol "SymbolName".
  2. Use the JSON output to answer questions with file:line-range evidence.

Expand your agent's capabilities with these related and highly-rated skills.

managedcode/RagSharp

ragsharp-build-code-graph

Build or update a code graph index for C#/.NET repositories using ragsharp-graph. Triggers: build index, update index, refresh index, code graph, dependency graph, static analysis, Roslyn, line numbers.

0 1
Explore
managedcode/RagSharp

ragsharp-mcp-code-graph

Run the ragsharp MCP JSON-RPC server and issue graph commands (doctor/index/update/query/export) for Codex/agent integrations. Triggers: mcp, json-rpc, code graph, references, index, query, export.

0 1
Explore
managedcode/MCAF

mcaf-architecture-overview

Create or update `docs/Architecture.md` as the global architecture map for a solution. Use when bootstrapping a repo, onboarding, or changing modules, boundaries, or contracts. Keep it navigational and use `references/overview-template.md` for scaffolding.

47 6
Explore
managedcode/MCAF

mcaf-human-review-planning

Plan a human review for a large AI-generated code drop by reading the target area, tracing the natural user and system flows, identifying the riskiest boundaries, and prioritizing the files a human should inspect first. Use when the codebase is too large to review line-by-line and you need a practical review sequence plus a prioritized file list.

47 6
Explore
managedcode/MCAF

mcaf-documentation

Create or refine durable engineering documentation: docs structure, navigation, source-of-truth placement, and writing quality. Use when a repo’s docs are missing, stale, duplicated, or hard to navigate, or when adding new durable engineering guidance.

47 6
Explore
managedcode/MCAF

mcaf-observability

Design or improve observability for application and delivery flows: logs, metrics, traces, correlation, alerts, and operational diagnostics. Use when a change affects runtime visibility, failure diagnosis, SLOs, or alerting.

47 6
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results