verification
Prove how code behaves before reporting it. Use before claiming that a change works, fails or is needed, in particular on another platform than the one you run on (like Windows from macOS).
Source facts
- Repository
- meta/docusaurus
- Last source activity
- November 5, 2026 at 16:37
- Detected SKILL.md language
- English
- Stars
- 66,681
- Forks
- 10,128
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- verification
- description
- Prove how code behaves before reporting it. Use before claiming that a change works, fails or is needed, in particular on another platform than the one you run on (like Windows from macOS).
# Verification
Report what you proved, not what you inferred. Don't present the result of reading the code, or of a local simulation, as a fact: run the code. Until you can, report it as unverified.
## Other platforms
You can't prove locally how code behaves on a platform you don't run on. For example, faking `process.platform` on macOS proves nothing about Windows: Node.js and third-party libraries still behave like on macOS.
Prove it on the real platform instead. For Windows, push a commit to a PR (a temporary one if needed, reverted afterwards) and let the Windows CI confirm or refute your assumption. It runs `pnpm test` and builds the website on Windows, but only when the PR changes a file matching its `paths` filter (see `.github/workflows/tests-windows.yml`).
View on GitHub