the signals and their derived score are provisional and subject to change.
validate manually before sharing.
48835c6660a7a3730b5a122bb7b88909997addbefa0235d533bd958ef196feb26079fe170a232163Authored: 3 weeks ago (Sat, 22 Aug 2026 19:10:42 +0000)Match: Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>c3eb7616b50a12a4ee9c4b0366ea85d7052130d7Authored: 1 month ago (Mon, 3 Aug 2026 14:01:39 +0000)Match: Co-authored-by: Claude Opus 5 <noreply@anthropic.com>7c3d461c9de0ab21fe4226e740374257e57b3e12Authored: 2 months ago (Sun, 12 Jul 2026 00:19:04 +0000)Match: Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>7adb36c7a7579887eb7799c0708a9c643155fcb6Authored: 2 months ago (Thu, 2 Jul 2026 12:09:27 +0000)Match: Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>CLAUDE.mdTool: claude-code# CLAUDE.md
## Write from the reader's state
Everything you write here outlives the context that produced it, and the
reader gets only what their artifact carries: a comment's reader sees the
file at one commit; a commit message's reader sees the commit and its
parent, so the change itself is visible but nothing else is. Neither
reader has the conversation, the review thread, or the session that
produced the text. Reference only what your reader can see; if a
referent lives anywhere else, restate it or drnone