Skip to content

[docs] Consolidate developer specifications into instructions file - #28702

Merged
pelikhan merged 1 commit into
mainfrom
docs/consolidate-developer-docs-2026-04-27-1531fc8f67246a18
Apr 27, 2026
Merged

pelikhan merged 1 commit into
mainfrom
docs/consolidate-developer-docs-2026-04-27-1531fc8f67246a18

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Maintenance tone scan v8.2 — fixed 2 subjective phrases in spec files.

Changes Made

  • Scanned all 64 spec files in scratchpad/ for marketing/subjective language
  • Fixed 2 tone issues across 2 files
  • Bumped scratchpad/dev.md to v8.2 with updated document history

Tone Fixes

File Before After
scratchpad/validation-architecture.md Developer-friendly warnings Non-critical diagnostic warnings
scratchpad/oh-my-code.md "coding on steroids" high-throughput automated code assistance

Validation

  • All 64 spec files scanned for marketing language, subjective adjectives, and informal phrases
  • No new spec files since previous run (v8.1, 2026-04-26)
  • scratchpad/dev.md version and history updated

Generated by Developer Documentation Consolidator · ● 438.3K · ◷

  • expires on Apr 29, 2026, 11:34 AM UTC

…iles

Fix informal/subjective language in validation-architecture.md and
oh-my-code.md to align with the project's technical documentation
tone standard.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions github-actions Bot added automation documentation Improvements or additions to documentation labels Apr 27, 2026
@github-actions

Copy link
Copy Markdown
Contributor Author

Hey @github-actions[bot] 👋 — thanks for the automated tone-scan maintenance! Replacing informal phrases like "coding on steroids" and "Developer-friendly warnings" with neutral, precise language keeps the spec files consistent and professional.

One thing to note:

  • No test coverage — the diff touches only documentation/spec files in scratchpad/, so automated test changes aren't strictly applicable here. However, if the project has any lint or prose-validation checks (e.g. a tone-linting script or a CI job that validates spec file formatting), confirming those pass would strengthen this PR's signal.

If you'd like a hand wiring up automated validation for future tone scans, here's a ready-to-use prompt:

Add a CI validation step (or extend an existing one) that runs a lightweight prose/tone linter (e.g. a custom script or a tool like `vale`) against files in the `scratchpad/` directory. The check should flag marketing adjectives, informal idioms, and subjective language, matching the patterns already being fixed by the maintenance tone-scan workflow. The check should run on every PR that modifies files under `scratchpad/`.

Generated by Contribution Check · ● 816K · ◷

@pelikhan
pelikhan merged commit 9d36179 into main Apr 27, 2026
@pelikhan
pelikhan deleted the docs/consolidate-developer-docs-2026-04-27-1531fc8f67246a18 branch April 27, 2026 13:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automation documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant