Treat the old README as evidence to verify not a template to preserve
Treat the old README as evidence to verify, not a template to preserve.
README generators often preserve stale claims or produce generic sections because they do not inspect the actual project or distinguish evidence from inference.
The skill may edit only the root README.
Features, commands, compatibility, status, URLs, metrics, and license terms cannot be invented.
Applications, packages, APIs, CLIs, monorepos, datasets, and skills require different reading flows.
Repository evidence inventory; project-type/quality references and authoring workflow; deterministic README checker plus npm installer/tests.
Repository evidence inventory.
Project-type/quality references and authoring workflow.
Deterministic README checker plus npm installer/tests.
Treat the old README as evidence to verify, not a template to preserve.
Classify facts as verified, inferred, or unknown.
Enforce a full-document output contract rather than allowing a badge-only or single-section patch.
Share your challenge, scope, and timeline to start a focused conversation.