Agent skill · Audited from source
Memtrace Change Impact Analysis
skill · syncable-dev/memtrace-publicNOASSERTION licenceAudited 22 Oct 2026 · source 2fb9c41f5af1
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 2fb9c41f5af1 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Compute what a planned source-code change will break — blast radius, affected processes, cross-repo callers, temporal stability, and Cortex decision-memory constraints — and produce a risk-rated change plan. Use for…
Cite
Cite this page
ModelsAtlas. “Memtrace Change Impact Analysis (syncable-dev/memtrace-public)”. Retrieved 22 Oct 2026. https://modelsatlas.com/skills/syncable-dev/memtrace-change-impact-analysis
Trust audit
Audit 0.4.1 · source read 22 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 17,406 of 18,389 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 2fb9c41f5af1 · 22 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publishersyncable-dev GitHub organizationOwner of the repository this skill is read from
- Source foldersyncable-dev/memtrace-public/plugins/memtrace-skills/skills/memtrace-change-impact-analysisThe exact folder we audited
- LicenceNOASSERTIONAs the repository states it
- Commit pinned for this verdict2fb9c41f5af1A new audit runs when the source changes
- Repository statusNot archivedPushed today
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Compute what a planned source-code change will break — blast radius, affected processes, cross-repo callers, temporal stability, and Cortex decision-memory constraints — and produce a risk-rated change plan. Use for…
---
name: memtrace-change-impact-analysis
description: "Compute what a planned source-code change will break — blast radius, affected processes, cross-repo callers, temporal stability, and Cortex decision-memory constraints — and produce a risk-rated change plan. Use for multi-symbol or multi-part edits, refactors, API changes, renames, removals, PR reviews, or risk assessments that need a plan; for one symbol's raw blast radius, call get_impact directly. Do not manually grep references or browse files for impact; use Memtrace graph context, change history, and decision recall/provenance."
---
## Overview
Pre-change risk assessment workflow. Before modifying code, this workflow maps the full blast radius, identifies affected processes, checks recent change history for instability signals, checks Cortex decision memory for recorded decisions/bans/contracts, and produces a risk-rated change plan.
Use this workflow when the change spans multiple symbols or needs a risk-rated plan. For a quick raw upstream/downstream radius around one known symbol, call `get_impact` directly.
## Steps
### 1. Identify what's being changed
Find the target symbol(s):
- Use `find_symbol` if the user named specific functions/classes
- Use `find_code` if the user described behaviour ("the authentication middleware")
Collect symbol **names** (`name`, `scope_path`, `file_path`) for all targets — graph tools use names, not internal IDs.
### 2. Get 360° context for each target
For each symbol, call `get_symbol_context` (`repo_id`, `symbol`, `file_path`):
- Direct callers and callees
- Community membership (which module is this in?)
- Process membership (which execution flows does this participate in?)
- Cross-repo API callers (is this an endpoint called by other services?)
**Decision:** If cross-repo API callers exist, this change requires coordination with other teams. Flag this immediately.
### 3. Compute blast radius
For each target, call `get_impact` (`repo_id`, `target`) with `direction: "both"`, `depth: 5`:
- Upstream impact: what depends on this symbol
- Downstream impact: what this symbol depends on
- Risk rating: Low / Medium / High / Critical
**Decision:**
| Risk | Action |
|------|--------|
| Low | Proceed with standard testing |
| Medium | Review all direct callers; test affected processes |
| High | Plan incremental migration; consider feature flags |
| Critical | Full migration strategy; backward-compatible changes required |
### 4. Check Cortex decision memory
For each target or subsystem, call `recall_decision("<target/subsystem/approach>")`.
If the graph result exposes a numeric `symbol_id`, also call
`why_is_this_here(symbol_id)` and `governing_contracts(symbol_id)`.
- Matching decision/ban/convention → include it in the plan before recommending a change.
- Decision you intend to rely on → run `verify_intent(decision_id)` first.
- CannotProve → record "no decision proven"; do not treat it as approval.
### 5. Check temporal stability
Call `get_evolution` (`repo_id`, `from: "30d ago"`, `mode: "compound"`), then `get_timeline` on each target symbol (requires `scope_path` + `file_path` from `find_symbol`):
- Sparse timeline history + you're about to change it → structurally surprising; extra scrutiny warranted.
- Target appears in `top_touched_symbols` → high churn + high impact = volatile hotspot.
### 6. Map affected execution flows
From step 2, you already know which processes are affected. For critical changes, use `analyze_relationships` (`repo_id`, `target`) with `query_type: "find_callers"` at `depth: 3` to trace the full transitive caller chain.
`depth: 3` is a JSON number, not a string — the validator rejects `"3"`.
Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root).
### 7. Produce the risk assessment
Synthesize into a change plan:
1. **Target(s)** — what's being changed and where
2. **Blast Radius** — number of direct/transitive dependents, risk rating
3. **Affected Processes** — which execution flows will be impacted
4. **Cross-Service Impact** — any external callers or consumers
5. **Stability Signal** — sparse `get_timeline` history (stable) vs frequent appearance in `top_touched_symbols` (volatile)
6. **Decision Memory** — relevant decisions/bans/contracts, or CannotProve as unknown
7. **Recommended Approach** — based on risk and decision constraints: direct change, incremental migration, or backward-compatible evolution
8. **Test Coverage** — which callers/processes to verify after the change
## Decision Points
| Condition | Action |
|-----------|--------|
| Risk = Critical | Recommend backward-compatible change + deprecation path |
| Cross-repo callers exist | Flag as requiring multi-service coordination |
| Symbol has sparse timeline but high impact | Extra review — this rarely changes; make sure the change is intentional |
| Multiple processes affected | List each affected flow; recommend testing each one |
| Symbol is a bridge point | Change may disconnect parts of the architecture — verify alternative paths exist |
| Cortex returns a held ban/contract | Do not recommend contradicting it without explicit user sign-off |
## Output
The workflow's artifact is the step-6 risk-rated change plan. Compact example:
```text
Target: AuthService::validateToken (src/auth/service.ts)
Blast Radius: 4 direct / 23 transitive dependents — Risk: High
Affected Processes: login-flow, session-refresh
Cross-Service Impact: 2 cross-repo API callers — needs multi-service coordination
Stability Signal: appears in top_touched_symbols (volatile hotspot)
Recommended Approach: incremental migration behind a feature flag
Test Coverage: all 4 direct callers + both affected processes
```Excerpt, first 5,762 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 2fb9c41
git clone https://github.com/syncable-dev/memtrace-public git -C memtrace-public checkout 2fb9c41f5af1
The author documents no install command, so this uses the repository directly. Our verdict covers commit 2fb9c41f5af1 only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
2fb9c41f5af1
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/syncable-dev/memtrace-change-impact-analysis/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
All coding & review skills →syncable-dev/memtrace-public
Map source-code relationships between symbols. Use when the user asks about callers, callees, references, imports, exports, type usages, class hierarchy, inheritance, implementations, overrides, or dependencies between…
syncable-dev/memtrace-public
Find source code with Memtrace hybrid BM25+semantic search: symbols, functions, classes, types, constants, definitions, implementations, logic, or error strings inside code. Use when the user wants to find, search,…
syncable-dev/memtrace-public
Catch up on everything that changed in an indexed source-code repo since the last session, using stored session anchors and Memtrace change memory. Use when the user asks to continue, catch up, resume, see what changed…
syncable-dev/memtrace-public
Index a source-code repo into the Memtrace knowledge graph and poll the job to completion. Use when the user asks to index, parse, ingest, reindex, watch, or prepare a source-code repo for Memtrace analysis, when code…
syncable-dev/memtrace-public
Find dead code, complexity hotspots, and refactoring candidates in indexed source code. Use when the user asks about source-code quality, dead code, unused functions, zero callers, complexity, cyclomatic complexity,…
syncable-dev/memtrace-public
Build a phased, risk-scored refactoring plan from Memtrace complexity, dead-code, bridge, impact analysis, and Cortex decision-memory constraints. Use when the user wants to refactor source code, reduce complexity,…
Add this badge to your README
[](https://modelsatlas.com/skills/syncable-dev/memtrace-change-impact-analysis/)
<a href="https://modelsatlas.com/skills/syncable-dev/memtrace-change-impact-analysis/"><img src="https://modelsatlas.com/skills/syncable-dev/memtrace-change-impact-analysis/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about Memtrace Change Impact Analysis
What does the Memtrace Change Impact Analysis skill do?
Is Memtrace Change Impact Analysis safe to install?
What can Memtrace Change Impact Analysis access on my machine?
What do I need installed to use Memtrace Change Impact Analysis?
How current is this page?
Sources
- github.com/syncable-dev/memtrace-public/tree/main/plugins/memtra — the audited source at commit 2fb9c41f5af1 and every finding aboveObserved · 22 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the Memtrace Change Impact Analysis skill do?
- Is Memtrace Change Impact Analysis safe to install?
- What can Memtrace Change Impact Analysis access on my machine?