Live survey304 models · 14 providers · 23,592 auditsAudited implement · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

Memtrace Code Review

skill · syncable-dev/memtrace-publicNOASSERTION licenceAudited 23 Oct 2026 · source 3e7894d935d8

★ 506pushed today
✓SAFEGrade B · 89/100 · 23 Oct 2026 · 3e7894d
506repo stars · whole syncable-dev/memtrace-public

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 3e7894d935d8 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Review GitHub pull requests with Memtrace's local graph-backed review engine. Use when the user asks to review a GitHub pull request, run Memtrace code review, post Memtrace review comments, create a PR with a review…

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Memtrace Code Review (syncable-dev/memtrace-public)”. Retrieved 23 Oct 2026. https://modelsatlas.com/skills/syncable-dev/memtrace-code-review

Trust audit

Audit 0.4.1 · source read 23 Oct 2026

Trust score89/100✓SAFE B
0 critical0 high0 medium0 low0 info

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

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS0
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

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 3e7894d935d8 · 23 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-code-reviewThe exact folder we audited
  • LicenceNOASSERTIONAs the repository states it
  • Commit pinned for this verdict3e7894d935d8A 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: Review GitHub pull requests with Memtrace's local graph-backed review engine. Use when the user asks to review a GitHub pull request, run Memtrace code review, post Memtrace review comments, create a PR with a review…

---
name: memtrace-code-review
description: "Review GitHub pull requests with Memtrace's local graph-backed review engine. Use when the user asks to review a GitHub pull request, run Memtrace code review, post Memtrace review comments, create a PR with a review step, or publish local graph-backed review findings to GitHub. Prefer the review_github_pr MCP tool over manual diff inspection. Do not use for local working-tree diffs — that is the built-in /code-review; this skill is for GitHub PRs via review_github_pr."
---

## Overview

Use Memtrace's local-first PR review workflow. The agent should call the `review_github_pr` MCP tool so review runs against the developer's local indexed graph, AST detectors, YAML rule pack, and review policy. GitHub is used for PR context and optional comment publication; source code analysis stays local.

## Default Flow

1. If the user gives a GitHub PR URL and asks to inspect or review it, call `review_github_pr` with `post: false`.
2. If the user explicitly asks to publish, post comments, or complete the PR review, call `review_github_pr` with `post: true`.
3. Use `graphMode: "strict"` by default. Use `graphMode: "off"` only when the user asks to benchmark non-graph behavior or the local graph is unavailable.
4. Default to `minSeverity: "high"` and `maxComments: 5` when posting. For previews, `maxComments: 10` is acceptable.
5. Pass `repoRoot` when the PR checkout is not the current working directory. Pass `repoId` when the indexed repository id is known.

Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root).

## Example User Prompts

- "Review this PR with Memtrace: https://github.com/OWNER/REPO/pull/123"
- "Use Memtrace to review this pull request and post the findings: https://github.com/OWNER/REPO/pull/123"
- "Create the PR, then run Memtrace code review and publish the review comments."

## Guardrails

- Do not start with generic grep, rg, or manual diff review when `review_github_pr` is available.
- Do not post comments unless the user explicitly requested publication.
- After posting comments (`post: true`), record the PR URL and the posted comment IDs in the session output as the audit trail.
- Do not create benchmark-specific or PR-specific findings. The review must come from general Memtrace detectors, graph evidence, and policy ranking.
- If the tool reports missing auth, tell the user to run `memtrace auth login`.
- If the tool reports missing GitHub App installation, tell the user to install Memtrace Code Reviewer on that repository.
- If the tool reports missing local graph context, tell the user to run
  `memtrace index .` from the actual repo root. If the open folder is a parent
  containing multiple independent repos, do not index the parent unless the user
  explicitly wants a shared workspace.

## Output

Summarize the `review_github_pr` result with these fields:

| Field | Preview (`post: false`) | Posted (`post: true`) |
|---|---|---|
| PR URL + repository | yes | yes |
| Graph state | yes | yes |
| Findings | count of candidate comments, plus file, line, severity, message per finding | number of comments posted |
| Posted comment IDs | — | yes — record with the PR URL as the audit trail |

Excerpt, first 3,269 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 3e7894d

Download folder ↗
git clone https://github.com/syncable-dev/memtrace-public
git -C memtrace-public checkout 3e7894d935d8

The author documents no install command, so this uses the repository directly. Our verdict covers commit 3e7894d935d8 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

  1. ✓SAFE B 89 / 100

    first audit · source 3e7894d935d8

Memtrace Relationships✓SAFE

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…

★ 509Grade B
Memtrace Search✓SAFE

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,…

★ 509Grade B
Memtrace Session Continuity✓SAFE

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…

★ 509Grade B
Memtrace Index✓SAFE

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…

★ 508Grade B
Memtrace Quality✓SAFE

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,…

★ 508Grade B
Memtrace Refactoring Guide✓SAFE

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,…

★ 508Grade B

Questions about Memtrace Code Review

What does the Memtrace Code Review skill do?
Structural memory for AI coding agents. Bi-temporal graph, MCP-native, zero LLM calls. Cursor · Claude Code · Codex · DeepSeek Harness · Hermes · VS Code · Windsurf.
Is Memtrace Code Review safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Memtrace Code Review access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (3e7894d935d8), read on 2026-10-23. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

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.