ワンクリックでManusで任意のスキルを実行

memtrace-code-review

スター425

フォーク36

更新日2026年7月9日 11:04

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.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

syncable-dev

syncable-dev/memtrace-public

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

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

If the user gives a GitHub PR URL and asks to inspect or review it, call review_github_pr with post: false.
If the user explicitly asks to publish, post comments, or complete the PR review, call review_github_pr with post: true.
Use graphMode: "strict" by default. Use graphMode: "off" only when the user asks to benchmark non-graph behavior or the local graph is unavailable.
Default to minSeverity: "high" and maxComments: 5 when posting. For previews, maxComments: 10 is acceptable.
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

このリポジトリの他の Skills

同じリポジトリ

memtrace-first

syncable-dev/memtrace-public

Route code discovery, debugging, flow tracing, how-code-works questions, and pre-edit rationale checks in indexed source-code repos to Memtrace graph plus Cortex decision tools. Use first before searching/reading code, and before editing, refactoring, deleting, or re-picking an approach that may have a recorded decision, ban, convention, or contract. Do not use Grep, Glob, rg, find, or manual file browsing for code discovery when Memtrace is indexed. Zero results are not permission to grep; diagnose/reindex with Memtrace.

2026-07-09425

memtrace-index

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 exploration needs an index, or when searches return 0/partial results for source paths under an indexed root. Use this before Grep, Glob, rg, find, or manual code search whenever the repo can be indexed. For ongoing watch mode / live re-indexing after the initial index, use memtrace-continuous-memory.

2026-07-09425

memtrace-change-impact-analysis

syncable-dev/memtrace-public

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 before edits, refactors, API changes, renames, removals, PR reviews, or risk assessments, especially when changing established behavior or deleting code. Do not manually grep references or browse files for impact; use Memtrace graph context, change history, and decision recall/provenance.

2026-07-07425

memtrace-decision-memory

syncable-dev/memtrace-public

Check Cortex decision memory through the normal Memtrace MCP tools — the umbrella entry point for decision recall, provenance (why is this here), intent verification, and governing contracts. Use before assuming WHY code exists, before any non-trivial edit/refactor/delete of existing code, before re-picking a library/pattern/architecture, or before contradicting an apparent convention. Route: free-text decisions/bans/conventions → memtrace-decision-recall; symbol lineage/contracts → memtrace-provenance; did the decision hold → memtrace-intent-verification. Do not guess rationale from the diff or git log.

2026-07-07425

memtrace-decision-recall

syncable-dev/memtrace-public

Recall ranked decisions, bans, and conventions from Cortex decision memory by free-text query through the normal Memtrace MCP server. Use when the user asks what was decided/chosen/rejected, whether there is a convention/ban/policy, and before any non-trivial edit/refactor/delete or re-picking a library, pattern, architecture, or subsystem behavior that may already be settled. Do not reconstruct decisions from git log or guesswork. To verify whether a known decision held, use memtrace-intent-verification; for symbol lineage/contracts, use memtrace-provenance.

2026-07-07425

memtrace-preflight

syncable-dev/memtrace-public

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 decisions.

2026-07-07425

name

memtrace-code-review

description

Overview

Default Flow

If the user gives a GitHub PR URL and asks to inspect or review it, call review_github_pr with post: false.
If the user explicitly asks to publish, post comments, or complete the PR review, call review_github_pr with post: true.
Use graphMode: "strict" by default. Use graphMode: "off" only when the user asks to benchmark non-graph behavior or the local graph is unavailable.
Default to minSeverity: "high" and maxComments: 5 when posting. For previews, maxComments: 10 is acceptable.
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