Conversation
Add a "no em dashes, be concise, plain language" standard that applies to published documentation and to comments Claude posts to people (GitHub, Jira, Asana, Slack). Repo infrastructure stays out of scope. - docs/contributing/style-guide.md: new "Concise, human phrasing" and "Dashes" subsections. - .claude/skills/sumo-style/SKILL.md: mirror the concision rule. - AGENTS.md: new "Output tone" section so the rules reach connector comments, where the sumo-style skill does not load. Covers DOCS-988 action item 2 (team guidelines). Action item 1 (humanizer vs sumo-style evaluation) captured in a ticket comment. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
4 tasks
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
1 participant
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.
Purpose of this pull request
Covers DOCS-988 action item 2 (team guidelines). Adds a plain-tone standard so Claude's output reads less like generic AI: no em dashes, no throat-clearing or filler, concise phrasing. It applies to two things: published documentation (all of
/docs), and comments or messages Claude posts to people through a connector (GitHub, Jira, Asana, Slack). Repo infrastructure (.github/,AGENTS.md,.claude/, source code, commit messages) stays out of scope.docs/contributing/style-guide.md: new Concise, human phrasing subsection under Voice and tone, and a Dashes subsection under Punctuation that bans the em dash while keeping the en dash for numeric and date ranges..claude/skills/sumo-style/SKILL.md: mirrors the concision rule in Gotchas (the em dash ban was already there).AGENTS.md: new Output tone section, so the rules also govern connector comments, where thesumo-styleskill does not load.DOCS-988 action item 1 (evaluate
/humanizeragainst/sumo-style) is captured in a comment on the ticket.A follow-up option, not in this PR: a PreToolUse hook could hard-enforce the em dash ban on
EditandWritetodocs/**and on comment-posting commands. Verbosity stays a soft rule.Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/DOCS-988
🤖 Generated with Claude Code