Skip to content

chore(docs): update README.md for consistent format and to avoid duplication - #23939

Merged
felixarntz merged 7 commits into
mainfrom
fa/readme-cleanup
Oct 23, 2026
Merged

felixarntz merged 7 commits into
mainfrom
fa/readme-cleanup

Conversation

@felixarntz

Copy link
Copy Markdown
Collaborator

Background

Package README.md files should be minimal starting points. Detailed documentation already lives in content/; duplicating it in READMEs risks drift.

Summary

  • Standardize READMEs around a title, brief description, install command, one usage example, and documentation links.
  • Preserve existing descriptions, selected examples, relevant callouts, and coding-agent skill sections; add docs-sourced examples where missing.
  • Add an edit-package-readme skill to capture the conventions.
  • Explicit format exceptions:
    • ai (also the repository README)
    • codemod (internal tooling)
    • provider, and provider-utils (internal foundations)

Checklist

  • All commits are signed (PRs with unsigned commits cannot be merged)
  • Tests have been added / updated (for bug fixes / features)
  • Documentation has been added / updated (for bug fixes / features)
  • A patch changeset for relevant packages has been added (for bug fixes / features - run pnpm changeset in the project root)
  • I have reviewed this pull request (self-review)

Future Work

Update the angular README once a suitable documentation page exists. It remains untouched for now, but is not a format exception.

Comment thread packages/policy-opa/README.md Outdated
Comment thread packages/workflow-harness/README.md
@felixarntz
felixarntz enabled auto-merge (squash) October 23, 2026 22:20
@felixarntz
felixarntz merged commit e729d58 into main Oct 23, 2026
52 checks passed
@felixarntz
felixarntz deleted the fa/readme-cleanup branch October 23, 2026 22:28
5. `## Usage`: only one fenced, basic getting-started code example (TypeScript or a framework component with TypeScript).
6. A suitable docs link using `See the [<package title> documentation](<url>) for more information.` If none clearly fits, use 1–2 related docs links with custom phrasing.

You must not include anything else in the readme. Any additional documentation belongs in `content/`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This rule contradicts the READMEs this PR produces. 45 of them keep a ## Skill for Coding Agents section between Setup and Usage (e.g. packages/anthropic/README.md:13, packages/openai/README.md:14, packages/gateway/README.md:11), and the PR description says keeping it is intentional. An agent following this skill literally will delete that section on the next edit, and new provider READMEs will leave it out.

Can we add it to the ordered list as an optional item between Setup and Usage, with the exact block, and say which packages get it (provider packages)?

Related: skills/add-provider-package/SKILL.md:164 still says to write the README with "installation, authentication, configuration, supported models, and basic usage", which this format now forbids. Pointing it at edit-package-readme would keep the two skills from pulling in opposite directions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants