Menu
Use when the user explicitly asks for a structural audit, architecture review, dead-code report, test-gap analysis, or evolution hotspot scan. Heavier and noisier than the other raysense skills — only run on demand, not as part of the routine edit loop.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use after a rescan to surface structural regressions across a time window. Diffs the latest scan against the saved baseline AND the trend history, ranking dimensions that worsened, files newly hot, and rules newly tripped. Configurable window (7d, 30d, 90d). Use periodically (daily, weekly, or pre-PR).
Use at the start of any coding session in a repository to scan the structure, save a baseline, and materialize splayed-table memory for fast follow-up queries. Establishes the "before" reference point that the verify skill diffs against later.
Use before refactoring, deleting, moving, or substantially modifying a file to compute its blast radius, coupling profile, and cycle exposure. Lets the agent edit with awareness of downstream effects rather than discovering them after the fact.
Use when the agent has a structural question about the saved baseline that the typed MCP tools (health, hotspots, rules, blast radius, coupling, cycles, evolution) do not directly answer. Runs Rayfall expressions against splayed baseline tables via raysense_baseline_query. Three modes are available - select queries for filter/project/aggregate (most common), .graph.* algorithms (PageRank, Louvain, topsort, shortest-path, betweenness, closeness, MST, k-shortest, BFS expand) for centrality and reachability over the call graph, and Datalog rules with transitive closure for declarative reachability ("reaches", "depends-on", "tainted-by"). Reach for this when the question shape is "files where X and Y," "most-central callers," "what does X transitively reach," or any custom slice across the 18 baseline tables.
Use after completing a logical chunk of edits to rescan the project and detect new rule violations or health regressions against the session baseline. Catches structural regressions before they reach review.
| name | audit |
| description | Use when the user explicitly asks for a structural audit, architecture review, dead-code report, test-gap analysis, or evolution hotspot scan. Heavier and noisier than the other raysense skills — only run on demand, not as part of the routine edit loop. |
This skill is for deliberate "look at the whole codebase" requests. It calls multiple raysense MCP tools and produces a multi-section report. Do not run it as part of routine edits — it is loud by design and will pollute the working context.
All tools take a path argument; pass the current repo root.
raysense_architecture. Reports root
causes, cycles by SCC, layer levels, and unstable modules. Lead
the report with the worst root cause.raysense_dsm for the module dependency matrix and
level assignments. Useful for showing the user the shape of the
project, not just the metrics.raysense_evolution. Surfaces bus factor,
change-coupling pairs (files that change together), and temporal
hotspots (commits × max complexity).raysense_test_gaps. Files without nearby
tests, ranked by risk.raysense_visualize if the user
asked for something they can browse. Writes a self-contained HTML
file the user can open.When summarising back to the user, lead with the one finding that matters most — usually the worst architectural root cause or the highest-risk untested file. Long lists overwhelm; a single prioritized headline plus a short table of next-three-things tends to land better.
impact or a
single targeted MCP call instead.raysense_health and read out the grade.The audit's typed tools surface what raysense already knows. When
the user asks an audit-shaped question that doesn't fit a typed
tool, the query skill exposes Rayfall directly via
raysense_baseline_query:
.graph.pagerank / .graph.louvain / .graph.betweenness over
call_edges or module_edges for centrality-based audits.raysense_baseline_import_csv to bring external audit data
(coverage, lint counts, test runtime) into the same query
substrate as the structural baseline.