docs: break up dense paragraphs in github-screenshots skill - #848
Conversation
Apply the docs restructure (#847) scannability treatment to the github-screenshots SKILL.md: split the bold-lead walls in Step 2 and the dev-server flags paragraph in Step 1 into short sentences and bulleted lists. Formatting only — every command, flag, and caveat is preserved.
|
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (2)
🚫 Excluded labels (none allowed) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Applies the docs restructure (#847) scannability treatment to the
github-screenshotsskill. Same failure mode the docs pass targeted: a bold lead-in followed by a 5–6 line run-on glued with em-dashes.Formatting only — every command, flag, and caveat is preserved.
--no-hide-dev-tools,--reduced-motion,--hide,--eval/--init-script).--state/--meta pathhabit, and the same-URL before/after contract; led thehintnote with its condition.Left Step 1's capture examples, the comment-assembly section, and the cautions alone — those already carry their weight with code blocks and existing bullets.