Skip to content

docs: align xml documentation and code comment policy - #151

Merged
senrecep merged 1 commit into
mainfrom
docs/xml-docs-vs-comments-policy
Oct 10, 2026
Merged

senrecep merged 1 commit into
mainfrom
docs/xml-docs-vs-comments-policy

Conversation

@senrecep

Copy link
Copy Markdown
Owner

What / why

AGENTS.md said "Don't add docstrings or comments unless explicitly asked" while CONTRIBUTING.md said to write XML docs for public APIs. Decision (per #146 item F): XML documentation comments (///) on public API are expected; inline code comments (//, /* */) explaining code are not.

Files: AGENTS.md, CONTRIBUTING.md, .claude/rules/csharp.md, .kimi/skills/csharp-conventions/SKILL.md (one line each, minimal wording).

Build enforcement (reality check)

Directory.Build.props sets GenerateDocumentationFile=true and NoWarn=1591, so XML docs are generated but missing docs on public members are NOT enforced (CS1591 suppressed). No CS1591/SA1600 entries in .editorconfig. About 482 of ~685 files declaring public types already contain ///. The policy is therefore a convention, not a build gate; no build config was changed. No XML docs added in this PR.

Evidence

Docs only; no code or tests changed. Red/green: n/a.

Behaviour change

None. No release (docs:).

Refs #146

🤖 Generated with Claude Code

AGENTS.md said no docstrings or comments while CONTRIBUTING.md asked for
XML documentation on public APIs. XML documentation comments on public
APIs are now expected everywhere; inline code comments that explain code
remain disallowed. No code or behaviour change.

Refs #146

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@codecov

codecov Bot commented Oct 10, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@senrecep
senrecep merged commit 5622435 into main Oct 10, 2026
10 checks passed
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.

1 participant