chore(rfc): wrap markdown at 120 columns and add RFC style rules to the rfc skill - #630
Merged
Conversation
Member
|
Good to have @filvecchiato review this. |
filvecchiato
approved these changes
Sep 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tooling for writing and reviewing RFCs in this repo. Used to write the RFC stack #631 → #632 → #633 → #634, which ends in the Input Modality RFC.
Markdown formatting
.prettierrcwraps Markdown prose at 120 columns (proseWrap: always). Sentences in RFCs and design docs land on stable lines, so a review diff shows the sentence that changed rather than a rewrapped paragraph. Prettier is not part of CI;npm run formatapplies it andnpm run format:checkverifies it.The
rfcskillThe skill gains a Style section that turns the review rules for RFCs into something the skill applies while drafting:
rust/crates/truapi/src/api/*.rs; a shared concept is defined in one RFC and linked from the others; inline lists are examples unless declared exhaustive.The mechanics section is reflowed to the new column width; its content is unchanged.