Skip to content

docs(claude): scope the generated-mirror rule to the files that are mirrors#3468

Draft
max-sixty wants to merge 1 commit into
mainfrom
shell-restart-detection
Draft

docs(claude): scope the generated-mirror rule to the files that are mirrors#3468
max-sixty wants to merge 1 commit into
mainfrom
shell-restart-detection

Conversation

@max-sixty

Copy link
Copy Markdown
Owner

The Documentation section of CLAUDE.md said "never hand-edit the generated mirrors under docs/content/, skills/worktrunk/reference/, or plugins/worktrunk/skills/", which reads as "everything under these directories is generated." That's wrong for two of the three:

  • docs/content/ — non-command docs (faq, tips-patterns, worktrunk, claude-code, llm-commits) are hand-edited primaries; only command pages have generated regions.
  • skills/worktrunk/reference/shell-integration.md, troubleshooting.md, and README.md are hand-maintained sources (already carved out in .gitattributes with linguist-generated=false); the rest are generated mirrors.
  • plugins/worktrunk/skills/ — wholly generated, as stated.

The over-broad wording nearly steered #3455 away from editing shell-integration.md, which was the correct file to edit. The reworded sentence names the split per directory and defers to docs/CLAUDE.md's sync taxonomy (already linked at the end of the paragraph) for the per-file answer. No behavior or generated-file changes.

This was written by Claude Code on behalf of Maximilian Roos

🤖 Generated with Claude Code

…irrors

The Documentation section read as "everything under docs/content/,
skills/worktrunk/reference/, and plugins/worktrunk/skills/ is generated",
but two of those directories also hold hand-edited primaries: non-command
docs in docs/content/ and skill-only pages (shell-integration.md,
troubleshooting.md) in the reference dir. Only plugins/worktrunk/skills/
is wholly generated. Name the split so the sentence stops steering edits
away from legitimate source files.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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