Skip to content

petrbouda/microscope

v1.0.33Apache-2.0

Analyze JVM recordings with a running Jeffrey Microscope — point it at a JFR file or heap dump to build a profile, then list analysed recordings, query their DuckDB tables, and pull flamegraph, trace and heap-dump exports without leaving the terminal.

report

The shape and the evidence rules for any performance finding drawn from a Jeffrey Microscope profile — what a finding must carry before it is worth writing down, how a figure is quoted and against what denominator, what caps a claim at medium confidence, and how the questions a recording cannot answer are reported apart from the findings. Use whenever writing up an analysis, summarising an investigation, answering "what did you find", or handing conclusions to another person or agent — after analyze-jfr, analyze-heap, compare-jfr, regression-check or optimize-code has done the reading, and just as much when the user brings findings from an earlier analysis and asks for them written up ("write that up for my team"), whose figures are read back from Jeffrey before they go into the report.

Read SKILL.md at the source

Pinned to revision 682c5d0574c6, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.