-
Notifications
You must be signed in to change notification settings - Fork 8
Agents.MD + style guide #292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR introduces a comprehensive technical writing style guide specifically designed for agents and LLMs to use when creating or reviewing Cloudsmith documentation. The guide consolidates Google style guide principles, Cloudsmith UX writing guidelines, and company-specific conventions into a single reference document.
Key changes:
- Establishes a clear precedence hierarchy for documentation standards (Cloudsmith-specific → Google → third-party references)
- Defines core principles including task-orientation, clarity, active voice, and scannability
- Provides extensive UX writing guidelines with before/after examples demonstrating best practices
Comments suppressed due to low confidence (1)
docs/agents.md:295
- The file ends with two blank lines (lines 294 and 295). According to the coding guidelines, files should typically end with a single newline character. This creates unnecessary whitespace.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| ### 3. Use plain language | ||
|
|
||
| - Write as simply as possible while remaining accurate e.g. "use" instead of "utilize". |
Copilot
AI
Dec 23, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing comma after "e.g." - it should be "e.g.," as per standard American English punctuation rules.
| - Write as simply as possible while remaining accurate e.g. "use" instead of "utilize". | |
| - Write as simply as possible while remaining accurate, e.g., "use" instead of "utilize". |
| - Use clear, descriptive headings | ||
| - Break up long paragraphs (aim for 3-5 sentences max) | ||
|
|
||
| ### Code Examples |
Copilot
AI
Dec 23, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The heading "Code Examples" uses title case capitalization but should use sentence case according to the style guide's own recommendation (section 6) that headings should "Capitalize only the first word and proper nouns in headings (sentence case)". It should be "Code examples".
| ### Code Examples | |
| ### Code examples |
| @@ -0,0 +1,294 @@ | |||
| # Technical Writing Style Guide for Agents | |||
Copilot
AI
Dec 23, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file is missing a copyright notice. According to the coding guidelines, most new source files should have a copyright comment near the top of the file in the format "Copyright 2025 Cloudsmith Ltd".
Added an agents.md which is really a style guide for agents: