Skip to content

coach: always read Workout Log page blocks for history questions#3

Merged
FrancescoCoding merged 1 commit into
masterfrom
claude/coach-workout-log-instruction-2nqt6i
Jul 21, 2026
Merged

coach: always read Workout Log page blocks for history questions#3
FrancescoCoding merged 1 commit into
masterfrom
claude/coach-workout-log-instruction-2nqt6i

Conversation

@FrancescoCoding

@FrancescoCoding FrancescoCoding commented Jul 21, 2026

Copy link
Copy Markdown
Owner

What and why

Adds a standing instruction to CLAUDE.md requiring the coach to fetch the full page body (blocks) of Workout Log entries before answering any question about past lifts or sessions. The database row properties hold only summary metadata; the actual sets, reps, weights, and notes live in the page blocks. Without this rule the coach could answer history questions from top-level fields alone and miss or misrepresent what actually happened in a session.

The instruction specifies the exact command (node scripts/notion.mjs get-page-blocks <pageId>) and requires the coach to explain concretely what occurred (exercises, loads, notes) rather than echoing property values.

Checklist

  • npm run lint, npm run build, and npm test pass locally
  • Docs updated where relevant (skill tables in CLAUDE.md)
  • No personal data, ids, or secrets in the diff
  • Change stays generic (useful beyond my own setup)

Generated by Claude Code

…stions

Adds a standing instruction to fetch the full page body (blocks) of
Workout Log entries before answering questions about past lifts or
sessions, not just the database row properties. The blocks hold the
real sets/reps/weights/notes; the coach must explain concretely what
happened in each session rather than reporting only top-level fields.
@FrancescoCoding
FrancescoCoding force-pushed the claude/coach-workout-log-instruction-2nqt6i branch from f2dce28 to 0bc7531 Compare July 21, 2026 10:54
@FrancescoCoding
FrancescoCoding merged commit ed48aa6 into master Jul 21, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant