Menu
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.
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 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.
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 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 | impact |
| description | 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. |
Call this before a non-trivial edit (deletion, rename, signature change, extraction, file move). It tells the agent what depends on the target and what the target depends on, so the edit plan can account for the blast radius up front.
All tools take a path argument (absolute, current repo root) plus
the target file path relative to that root.
raysense_blast_radius with path: <cwd>
and file: <target>. Returns the set of files reachable downstream
under the active edge filter. A blast radius >20 files is a strong
signal to break the change into smaller commits.raysense_coupling. Look up the
target's module in the response: afferent (incoming) and efferent
(outgoing) counts, plus main-sequence distance. High-afferent
modules are stable foundations — breaking changes there cascade
widely.raysense_cycles. If the target appears
in any reported cycle, call
raysense_break_cycle_recommendations for ranked candidate edges
to remove. The recommended edge is often not the obvious one.raysense_what_if to preview
the health delta without touching the working tree.instability score — a value near 1.0 means the file is
expected to depend on stable foundations, not be one.For cases the typed tools above don't cover, the query
skill exposes Rayfall directly via raysense_baseline_query:
(reaches ?a ?b) plus a recursive arm gives the same shape as
raysense_blast_radius but with a rule the agent picks at query
time..graph.shortest-path / .graph.k-shortest for path-aware impact
("which call paths reach this entry point") that go beyond the
blast-radius set.call_edges and change_coupling /
file_ownership to weight blast radius by author / commit history.