rh-ssg-formatting
Skill4 starsChanged 4 months agoApache-2.0View on GitHub
Review Red Hat documentation for SSG formatting compliance — code blocks (one command per step, bold via subs="+quotes", separate input/output), user-replaced values (angle brackets, italics, underscores), sentence-style capitalization in titles, product name/version attributes (not hard-coded), date formats ("3 October 2019"), single-step procedures (bullet not number), non-breaking spaces in "Red Hat", and man page references. Use this skill when checking Red Hat docs for code block formatting, placeholder values, title capitalization, product name attributes, or date formats.
In this repository53 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- action-commentsSkill
- article-extractorSkill
- docs-convert-gdoc-mdSkill
- docs-orchestratorSkill
- docs-review-content-qualitySkill
- docs-review-modular-docsSkill
- docs-review-securitySkill
- docs-review-styleSkill
- docs-review-technicalSkill
- docs-ticket-readinessSkill
- docs-workflow-code-analysisSkill
- docs-workflow-create-jiraSkill
- docs-workflow-create-merge-requestSkill
- docs-workflow-jira-readySkill
- docs-workflow-pipeline-diagnosticsSkill
- docs-workflow-planningSkill
- docs-workflow-pr-analysisSkill
- docs-workflow-quality-gateSkill
- docs-workflow-requirementsSkill
- docs-workflow-scope-req-auditSkill
- docs-workflow-security-reviewSkill
- docs-workflow-startSkill
- docs-workflow-style-reviewSkill
- docs-workflow-tech-reviewSkill
- docs-workflow-writingSkill
- git-pr-readerSkill
- ibm-sg-audience-and-mediumSkill
- ibm-sg-language-and-grammarSkill
- ibm-sg-legal-informationSkill
- ibm-sg-numbers-and-measurementSkill
- ibm-sg-punctuationSkill
- ibm-sg-referencesSkill
- ibm-sg-structure-and-formatSkill
- ibm-sg-technical-elementsSkill
- jira-readerSkill
- jira-writerSkill
- learn-codeSkill
- lint-with-valeSkill
- mdita-writeSkill
- query-codeSkill
- redhat-docs-tocSkill
- rh-ssg-accessibilitySkill
- rh-ssg-grammar-and-languageSkill
- rh-ssg-gui-and-linksSkill
- rh-ssg-legal-and-supportSkill
- rh-ssg-release-notesSkill
- rh-ssg-structureSkill
- rh-ssg-technical-examplesSkill
- rn-known-issuesSkill
- understand-pull-requestSkill
- validate-plugin-prereqsSkill
The file
Files
Red Hat SSG: Formatting review skill
Review documentation for formatting compliance with the Red Hat Supplementary Style Guide.
Checklist
Commands in code blocks
- Each code block contains only one command per procedure step
- Command input and example output are in separate code blocks
- Commands in code blocks use bold formatting (via
subs="+quotes") - Bold formatting is applied consistently, even when no output is shown
- Callouts are not used — use definition lists or bulleted lists after the code block instead
Explanation of commands and variables
- Single command/variable explanations use a simple sentence after the code block
- Multiple variables are explained with a definition list introduced by "where:"
- Each variable description begins with "Specifies"
- Parameters are listed in the order they appear in the code block
- YAML structure explanations use a bulleted list
User-replaced values
- User-replaced values use angle brackets:
<value_name> - Multi-word values use underscores:
<cluster_name> - Values are lowercase (unless surrounding text is uppercase)
- Values are italicized in running text
- In code blocks,
subs="+quotes"is used to enable italics - For XML code blocks, format is
${value_name}(not angle brackets)
Titles and headings
- All titles and headings use sentence-style capitalization (not headline-style)
- Guide titles, Knowledgebase article titles all follow this rule
Product names and version references
- Product names use AsciiDoc attributes, not hard-coded names
- Product versions use attributes, not hard-coded version numbers
- Hard-coded versions are used only for versions that never change (e.g., "introduced in RHEL 8.4")
- Attribute file is included in
master.adoc
Date formats
- Dates use "day Month year" format: "3 October 2019" (preferred)
- "Month day, year" format ("October 3, 2019") is acceptable if the preferred format causes clarity issues
Single-step procedures
- Procedures with only one step use an unnumbered bullet, not a numbered list
Non-breaking spaces
- Non-breaking space (
) is used between "Red" and "Hat" to prevent line breaks splitting the company name
Man page references
- Man pages referenced as:
_command_(section)man page on your system - No external links to man page websites
How to use
- Review only changed content and necessary context
- For each issue found, cite the relevant SSG section
- Mark issues as required (incorrect user-replaced values, missing bold in code blocks) or [SUGGESTION] (improvements)
Example invocations
- "Review formatting in this procedure module"
- "Check code blocks and user-replaced values in proc_installing.adoc"
- "Do an SSG formatting review on the changed files"
References
For detailed guidance, consult:
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

