Verification

GPTClaudeDeepSeek··▲ 1,371 copies·updated 2026-07-14

verification.prompt

# Verification

Verify the doc refactor.

Checks:
1) Confirm the target structure exists.
2) Confirm no content was deleted (only moved/archived).
3) List any remaining duplicates or orphan docs not referenced anywhere.
4) Search for broken links to docs and propose fixes.
5) Give a blunt verdict: clean / mostly clean / not clean, with the top fixes.

Output — write to file (required):
- Create: docs/audit/DOC_REFACTOR_VERIFY_<YYYY-MM-DD>.md
- Do NOT dump the full report in chat. Chat should only confirm the file was written + the verdict line.

DOC_REFACTOR_VERIFY file structure:
- Verdict: clean | mostly clean | not clean
- Structure check (pass/fail per expected file)
- Content preservation check (any deletions found)
- Duplicates / orphans list
- Broken links + proposed fixes
- Top fixes (if verdict is not "clean")

Output checklist (non-negotiable):
- [ ] docs/audit/DOC_REFACTOR_VERIFY_<YYYY-MM-DD>.md written
- [ ] Chat confirms file path + verdict only

when to use it

Community prompt sourced from the open-source GitHub repo kylehuirevvision/repo-rails (MIT). A "Verification" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.