Give each install path its own heading in the README - #25
Merged
Merged
Conversation
The Install section led each path with a bold sentence fragment, which reads as one wall of prose and leaves nothing for the sidebar outline to link. Make the three paths h3 headings and move the qualifier into the sentence below.
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
2 participants
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.
What this changes, and why
The Install section led each of its three paths with a bold sentence fragment
(
**Claude Code.**,**Any agent with the skills CLI**,**Codex, Copilot CLI, OpenCode**). Bold text is not structure: the section reads as one block of prose, GitHub'ssidebar outline shows a single "Install" entry, and there is no anchor to link someone
straight to the path they need.
Each path is now an
h3, with the trailing qualifier moved into the sentence underneath sothe heading stays a name rather than half a sentence.
## Installand its#installanchor are unchanged, so the header nav link still lands in the right place, and the h3s
sit at the same level as the
### 💬prompt callouts further down.Documentation only: no code, no version bump.
How you know it works
uv run python scripts/validate.pypasses. Read the section back as rendered markdown:three headings, the code blocks and the auto-update note untouched, and the same content in
the same order as before.
Checks that are easy to miss
skills/slideops/scripts/. Those two files run on a stranger's barepython3with nothing installed, and CI has a job that proves it.dist/skill-demo.pdfis not in the diff. It is a release asset, not a tracked file,and a plugin pays to download the tree on every update.
skills/slideops/references/style-guide.mdhas thereplacements.
Generated by Claude Code