Check technical claims against documentation and test records

Supply a technical draft, software versions and real test records to map claims to evidence and suggest small, reviewable corrections.

Execution environment and usage

AI / software

Gemini

Where to operate

The Gemini web-chat input; this version requests a text draft.

Getting started

  1. Open an eligible account at gemini.google.com and start a chat without connecting external accounts.
  2. Provide a shareable draft, software versions, approved docs and actual test results.
  3. Request the draft/check and compare it with the original material. Suggestions are not evidence of execution.

Setup and plan requirements

Task inputs: Provide a shareable draft, software versions, approved docs and actual test results. Use an eligible tool that can read the supplied format; verify parsing, context limits and access before relying on it.

Prompt portability limits

The written request can be adapted to a chatbot that accepts the same input. It does not transfer the original agent, plugins or computer permissions.

Usage limitations

Supply exact software versions, official-document excerpts or readable links and real test records; label unexecuted code accordingly.This independent pass reviewed local case records, without revalidating original sources or hands-on testing.

Environment sources

適用情境 / When to use

Supply a technical draft, software versions and real test records to map claims to evidence and suggest small, reviewable corrections. Supply exact software versions, official-document excerpts or readable links and real test records; label unexecuted code accordingly. Original case: The account describes a custom critique command.

步驟 / Steps

  1. Provide a shareable draft, software versions, approved docs and actual test results.
  2. Map technical claims to documentation or tests, separating suggestions from established errors.
  3. Have the author verify citations and reproducibility while preserving personal experience.

提示詞 / Prompt

Review [technical draft] against [versioned official docs] and [actual test records]. Build a claim-check table with evidence, questions and minimal suggested changes. Say when code was not run. Preserve [audience/tone/length requirements] and genuine personal experience; do not publish or fabricate results.

留意事項 / Cautions

  • Reading code is not evidence it ran successfully.
  • Do not invent the author’s tests or experiences.

來源限制 / Evidence limits

No error-detection rate is provided and individual suggestions may be wrong.

流程說明 / Workflow note

These steps and prompts are original, untested exercises by this site, not the author’s verbatim workflow. Reported results do not guarantee exercise outcomes.

原始工具組合 / Original tool stack

Gemini CLI; Gemini 3 Pro Preview; technical blog drafts

Source publication date: 2025-12-20

Source checked: 2026-10-19

Automating DevRel: How I Use Gemini CLI and Gemini 3 to Catch Bugs in My Blog Posts