Skip to content

Document the README + HISTORY cspell CI scope in CODESTYLE - #44

Merged
ptr727 merged 2 commits into
developfrom
docs/cspell-ci-scope
Jul 15, 2026
Merged

Document the README + HISTORY cspell CI scope in CODESTYLE#44
ptr727 merged 2 commits into
developfrom
docs/cspell-ci-scope

Conversation

@ptr727

@ptr727 ptr727 commented Jul 15, 2026

Copy link
Copy Markdown
Owner

Docs-only: append a new "Spelling CI scope" list item to CODESTYLE.md documenting that the CI spell-check gate covers README.md + HISTORY.md only (not all markdown), with broad live checking left to the cspell editor extension. Propagates the rule from the template (ptr727/ProjectTemplate#302, #303).

🤖 Generated with Claude Code

Propagate the CODESTYLE "Spelling CI scope" rule from the template
(ptr727/ProjectTemplate#302, #303): the CI spell-check gate covers
README.md + HISTORY.md, not all markdown, with broad live checking left
to the editor extension.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 15, 2026 17:43

Copilot AI left a comment

Copy link
Copy Markdown

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 updates the repository style guide to document the intended CI spelling gate scope for markdown, clarifying that the enforced CSpell check is limited to the visitor-facing docs rather than all *.md files.

Changes:

  • Add a new CODESTYLE.md guideline item describing the CI spelling gate scope (README.md + HISTORY.md only).
  • Explain the rationale for not gating all markdown files in CI and relying on editor spell-check for broader coverage.

Comment thread CODESTYLE.md Outdated
Copilot review: the item referenced a Lint: Spelling VS Code task and an
AGENTS.md cspell one-liner that exist in the template but not in this
repo. Reword generically so the guidance is accurate regardless of which
local cspell surfaces a repo actually has.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@ptr727
ptr727 merged commit e4b33bb into develop Jul 15, 2026
@ptr727
ptr727 deleted the docs/cspell-ci-scope branch July 15, 2026 17:55
ptr727 added a commit that referenced this pull request Jul 22, 2026
* Document the README + HISTORY cspell CI scope in CODESTYLE

Propagate the CODESTYLE "Spelling CI scope" rule from the template
(ptr727/ProjectTemplate#302, #303): the CI spell-check gate covers
README.md + HISTORY.md, not all markdown, with broad live checking left
to the editor extension.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* Reword the cspell-scope item to not name template-only surfaces

Copilot review: the item referenced a Lint: Spelling VS Code task and an
AGENTS.md cspell one-liner that exist in the template but not in this
repo. Reword generically so the guidance is accurate regardless of which
local cspell surfaces a repo actually has.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ptr727 added a commit that referenced this pull request Jul 22, 2026
* Document the README + HISTORY cspell CI scope in CODESTYLE

Propagate the CODESTYLE "Spelling CI scope" rule from the template
(ptr727/ProjectTemplate#302, #303): the CI spell-check gate covers
README.md + HISTORY.md, not all markdown, with broad live checking left
to the editor extension.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* Reword the cspell-scope item to not name template-only surfaces

Copilot review: the item referenced a Lint: Spelling VS Code task and an
AGENTS.md cspell one-liner that exist in the template but not in this
repo. Reword generically so the guidance is accurate regardless of which
local cspell surfaces a repo actually has.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants