Docs versus code
Find statements in the docs that the code now contradicts: quote the doc, show the code, and say which of the two is wrong.
In Lobstack: Skills › Library › Add
What your agent will do.
A README, guide or API reference may have fallen behind the code, or a release changed behaviour and nobody checked the pages that describe it.
- 01
Pick out the statements that can be checked: install steps, commands, flags, config keys, defaults, API fields, limits, error messages. Skip background and opinion.
- 02
For each one, find and read the code that decides it — the default value, the option parser, the handler. Another doc page is not a check.
- 03
Run what is safe to run: install steps in a scratch folder, the help output, a read-only API call. A documented command that fails is the strongest finding there is.
- 04
For each disagreement, quote the doc line, show the code line with its file, and say which one is wrong. Sometimes the doc is the intent and the code is the bug.
- 05
Ignore wording, tone and formatting. Only false statements count.
- 06
List documented features you cannot find in the code at all. A page for something that no longer exists is the costliest kind of drift.
- 07
Post a document, most misleading first. Offer the fixes on a branch, and ask before pushing or opening a pull request.
Quote both sides every time, so a reader can settle it without trusting you.
The whole SKILL.md: 34 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: docs-drift-reportdescription: "Find statements in the docs that the code now contradicts: quote the doc, show the code, and say which of the two is wrong."metadata: title: "Docs versus code" category: engineering tags: [docs, accuracy]--- ## When to use this A README, guide or API reference may have fallen behind the code, or a releasechanged behaviour and nobody checked the pages that describe it. ## How 1. Pick out the statements that can be checked: install steps, commands, flags, config keys, defaults, API fields, limits, error messages. Skip background and opinion.2. For each one, find and read the code that decides it -- the default value, the option parser, the handler. Another doc page is not a check.3. Run what is safe to run: install steps in a scratch folder, the help output, a read-only API call. A documented command that fails is the strongest finding there is.4. For each disagreement, quote the doc line, show the code line with its file, and say which one is wrong. Sometimes the doc is the intent and the code is the bug.5. Ignore wording, tone and formatting. Only false statements count.6. List documented features you cannot find in the code at all. A page for something that no longer exists is the costliest kind of drift.7. Post a document, most misleading first. Offer the fixes on a branch, and ask before pushing or opening a pull request. Quote both sides every time, so a reader can settle it without trusting you.
- Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App - Engineering
Pull request description
Write a pull request description from the diff: why it exists, what changed, how it was tested, and where a reviewer should look first.
SKILL.md · App - Engineering
Incident postmortem
Write a blameless postmortem from an incident's alerts, logs and chat: timeline, impact, root cause, and actions with owners.
SKILL.md · App - Engineering
Reproduce a bug before fixing it
Fix a bug by reproducing it first: turn the report into a failing test or script, shrink it, make the smallest fix, and show the test pass.
SKILL.md · App