Skip to content

docs: map each kind of text to its style guide section - #13667

Open
0x6e wants to merge 1 commit into
masterfrom
nathan/writing-style-guide-updates
Open

0x6e wants to merge 1 commit into
masterfrom
nathan/writing-style-guide-updates

Conversation

@0x6e

@0x6e 0x6e commented Sep 25, 2026

Copy link
Copy Markdown
Collaborator

List compiler diagnostics and commit messages in the guide's scope, and say which section applies to each kind of text.

Add Code Comments rule 7 on applying rule 6 to a whole comment. This comes from a personal Claude skill which I have found to be effective at reducing Claudish in my commits.


I intend to upstream the skill itself too, but wanted to move this "rule" part of the skill into the writing guide first. The skill will end up in a generic location with symlinks for different AI tools.

List compiler diagnostics and commit messages in the guide's scope,
and say which section applies to each kind of text.

Add Code Comments rule 7 on applying rule 6 to a whole comment. This
comes from a personal Claude skill which I have found to be effective at
reducing Claudish in my commits.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

@tronical tronical left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel that Opus 5 needed a ton of these instructions to get something somewhat readable and acceptable, but IME in other repos, 5.5 is hundred times better even by itself. I hope that in the mid term we can reduce these rules again (and spend less tokens).

Anyway, just a thought. Your change is of course very welcome:)

This branch was successfully deployed

1 active deployment
pr-preview-13667 — f2a80686 Deployed Sep 25, 2026 by github-actions[bot]
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.

2 participants