memtrace-code-review

## 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` ...