PhraseryPhrasery homeGet Phrasery
Documentation21 categories

Audit these docs for what is no longer true

Documentation that was written once and never checked against the code again.

Longauditmaintenancereview
Compare the documentation below against the code or product as it is now, and find what has gone stale.

Report in four groups:
- **Wrong**: statements that are now false. Quote the sentence and the code that contradicts it
- **Outdated**: flags, endpoints, filenames, or versions that have been renamed, moved, or removed
- **Missing**: behaviour that exists but is documented nowhere
- **Suspicious**: statements you cannot verify from what I gave you, with the specific thing I should check

Also flag: examples that would no longer run, links likely to be dead, screenshots described in text that no longer match, and anything dated by a phrase like "coming soon" or "currently".

Rank the findings by how much damage each does to a reader who trusts it. Do not rewrite anything yet.

Docs:
Code or current behaviour:

Making it yours

  • Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
  • Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
  • If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.

Editing and auditing docs. Finding what is stale or undocumented, cutting what the code already says, rewriting for the reader.

Related prompts

Keep this one

Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.

Add to your browser โ€” free