From 4d8ba0fc5e516463e17ac12040377e5d94d7389b Mon Sep 17 00:00:00 2001 From: Jean-Pierre Martineau Date: Sun, 6 Sep 2026 01:18:10 -0400 Subject: [PATCH] The profiling skill stops pointing at a file that is gone .claude/plans/ is deleted from the working tree along with the notes it held. The profile-picocalc skill closed on "where the numbers live", naming responsiveness.md; it now says to put the baseline, the breakdown and the tour in the commit message of the change they justify, where a number stays attached to the diff that earned it. Co-Authored-By: Claude Opus 5 (1M context) --- .claude/skills/profile-picocalc/SKILL.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.claude/skills/profile-picocalc/SKILL.md b/.claude/skills/profile-picocalc/SKILL.md index c22745a..3245657 100644 --- a/.claude/skills/profile-picocalc/SKILL.md +++ b/.claude/skills/profile-picocalc/SKILL.md @@ -156,5 +156,7 @@ have to come from touching fewer rows, not from composing faster. ## Where the numbers live -`.claude/plans/responsiveness.md` records the 2026-08-09 baseline, the per-stage breakdown, -and what is still open. Update it after a profiling pass rather than starting a new file. +There is no tracked results file. Put the baseline you measure, the per-stage breakdown, +and anything left open into the commit message of the change they justify — a number that +travels with its diff stays true, and one in a side file drifts. Quote the before/after +pair and the tour you ran, so the next pass can A/B against it.