memorydetective-plugin

Claude Code plugin marketplace for memorydetective: iOS leak hunting + performance investigation as a one-command install.

Install

/plugin marketplace add carloshpdoc/memorydetective-plugin
/plugin install memorydetective@memorydetective-plugin

That's it. You get:

• The memorydetective MCP server auto-registered (pulled from npm via npx)
• 42 MCP tools + a /perf-investigate skill for disciplined investigation
• 7 slash commands (/investigate-leak, /investigate-hangs, /investigate-jank, /investigate-launch, /verify-cycle-fix, /summarize-trace, /investigate-metrickit for MetricKit post-mortems)
• 34 cycle-pattern resources browsable at memorydetective://patterns/{patternId}, every classification carrying fixHint + staticAnalysisHint + fixTemplate (Swift before/after snippet)
• Recent headlines: v1.18 added analyzeMetricKitPayload (42nd tool, post-mortem production diagnostics from Apple MetricKit .mxdiagnostic JSON: crash clusters, hang hotspots with localized-duration parsing, CPU + disk exceptions) plus audit-close trio (open-enum SupportStatusKind, schemaDiscovery cache for 600-3000ms wall-clock win on summarizeTrace, local-only integration tests against real Apple .trace bundles). v1.17 reliability pass (strtobool env truthy parsing, verifyFix whitelist match modes, Instruments.app AppleScript document query that catches traces saved outside watchDir, fault-tolerant inspectTrace fallback, configurable countAlive framework-noise filter). v1.16 unblocked macOS 26.x trace recording via recordViaInstrumentsApp. v1.15 added the trace-side schema-coverage trio. v1.13 shipped summarizeTrace + /summarize-trace MCP prompt.

Full docs: plugins/memorydetective/README.md.

Why a plugin AND an npm package?

Both are first-class. Plugin is for Claude Code's native UX (zero-friction install + slash commands). The npm package is universal: install it directly to use with Cursor, Cline, Claude Desktop, Continue, or any MCP-compatible client.

The plugin wraps the npm package; it doesn't fork it. Single source of truth on npm, single repo for code.

Repo layout

memorydetective-plugin/
├── .claude-plugin/
│   └── marketplace.json           ← marketplace catalog (lists 1 plugin)
└── plugins/
    └── memorydetective/
        ├── .claude-plugin/
        │   └── plugin.json        ← plugin manifest (v1.18.0)
        ├── .mcp.json              ← MCP server registration (npx pulls from npm)
        ├── skills/
        │   └── perf-investigate/
        │       └── SKILL.md       ← /perf-investigate skill body
        ├── README.md
        ├── LICENSE
        └── CHANGELOG.md

Versioning

Plugin tracks the MCP server's minor version. memorydetective-plugin@1.18.x pulls memorydetective@^1.18 via npx. Patch releases are auto-resolved without bumping the plugin. Major server bumps (e.g. 2.0.0) require a plugin manifest update.

Source

• Plugin (this repo): https://github.com/carloshpdoc/memorydetective-plugin
• MCP server: https://github.com/carloshpdoc/memorydetective
• npm: https://www.npmjs.com/package/memorydetective

Privacy

memorydetective runs entirely on your machine. The MCP server is launched locally via npx, processes .memgraph and .trace files from your disk, and shells out to local tools (xcrun, sourcekit-lsp). No telemetry, no analytics, no data leaves your machine.

License

Apache-2.0. See LICENSE.