Skip to content

v1.18.2: /investigate-metrickit prompt + 7th MCP prompt

Latest

Choose a tag to compare

@carloshpdoc carloshpdoc released this 24 May 03:19
· 2 commits to main since this release

Post-v1.18.1 follow-up. Adds the /investigate-metrickit MCP prompt (the 7th, completing the prompt surface for the v1.18 MetricKit lane) and syncs the README prompt count which had drifted (stale at 5, actual 7 including /summarize-trace and the new MetricKit prompt). No tool API changes. 757 -> 758 tests (+1).

Added

  • /investigate-metrickit MCP prompt (7th prompt). Bespoke render (not playbook-backed). Takes a payloadPath argument and produces a ready-to-execute brief: 4 read-priority sections (crashCluster, hangHotspots, cpuExceptions, diskWriteExceptions), suggestedNextCalls chain hints into findCycles / analyzeHangs, and explicit constraints (no symbolication, no direct fix from raw .mxdiagnostic, payloadCount: 0 is a valid state). Surfaces in Claude Code as /investigate-metrickit. Prompt count goes from 6 to 7. Asserted via bespoke = ["summarize-trace", "investigate-metrickit"] filter in the playbook-backed coverage test.

Changed

  • README prompt count synced. The README listed 5 prompts (stale snapshot from v1.16) when actual count is 7. Updated to enumerate all 7 prompts, including /summarize-trace (v1.17) and the new /investigate-metrickit.