Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →syncable-dev/memtrace-preflight
Run a one-call pre-flight check on a single existing symbol before editing it: blast radius, co-change partners, complexity, 30-day churn, and verification checklist, then check Cortex decision memory for rationale/bans when intent may matter. Use before modifying any existing function or symbol you did not just write. Do not start editing a non-trivial existing function without pre-flight plus decision-memory recall/provenance; Memtrace knows the dependency graph, change history, and recorded d
Passed 14 of 17 test cases with the skill, and 7 of 17 without it.
and 12 more in the full report
10 fixed8 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
The initial preflight radar for `process_refund` in `orders-repo` flagged a `HIGH` risk level due to a broad dependent graph. I need to see the complete expanded list of affected downstream symbols beyond the top-level count. Which tool should I invoke next for this deeper inspection?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends calling get_impact for a deeper blast-radius analysis. | Missed | Passed |
The instructions your model reads when the skill loads.
Pre-flight check: the two minutes before an edit that prevent the bug. One
preflight_check call composes the dependency graph, the bi-temporal change
history, and the complexity metrics into an actionable radar for a single
symbol.
| Tool | Purpose |
|---|---|
preflight_check | Full radar for one symbol: blast radius + co-change + churn + checklist |
get_impact | Deeper blast-radius walk when the radar flags HIGH/CRITICAL |
get_cochange_context | Wider co-change window when partners look surprising |
recall_decision | Recorded choices, bans, and conventions for the symbol/subsystem/behavior |
why_is_this_here / governing_contracts | Symbol-scoped rationale and constraints when a symbol id is available |
Parameter types: MCP parameters are strictly typed. Numbers must be
Full parameter spec for every Memtrace tool: references/mcp-parameters.md (bundled at the memtrace-skills plugin root).
JSON numbers — not strings.
preflight_check with:
repo_id — requiredsymbol — the function/method name you are about to modifyEach line names something concrete to verify:
get_impact again after your edit and
compare total_affected; new dependents mean your change leaked wider
than intended.test cases passed, vs 7 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.