Gemini 4 Argon: Evidence-Based Bug Review and Minimal Patch
You’ll be able to separate demonstrated code failures from hypotheses and request a minimal patch. Keep source traces, candidate regression tests and real execution evidence together.
Make it yours
Fill in the inputs. Your prompt updates as you type.
Before you paste
Attach only code you own or are authorized to review, with relevant tests, dependency versions and configuration. Remove credentials and private records.
Your prompt
Review the attached authorized source and tests for vulnerabilities and logic failures.
Runtime and dependencies: {{tech_stack_and_versions}}
Exposure and trust boundary: {{exposure_level}}
Ignore stylistic lint. Focus on authentication/authorization errors, races, state corruption and unhandled input boundaries.
For each finding provide: evidence status DEMONSTRATED or HYPOTHESIS; severity with rationale; relevant CWE only when the classification is justified; exact source file/line and input-to-failure trace; a complete safe local regression test; and the smallest candidate patch.
Do not invent missing files, executed tests or successful exploits. If execution is unavailable, label the test NOT RUN and explain what result would establish the issue. Keep demonstrations in a fictional/local test environment; do not target public systems. Preserve unrelated behavior and wait for actual verification output.2 inputs still blank. Empty inputs stay as placeholders when copied.
Get one tested prompt a week
One workflow, one prompt, one tool and one quality check by email. No spam, unsubscribe any time.
By subscribing you agree to receive this email from Genius Forges and to us storing your address to send it. We may ask you to confirm by email. Every email has an unsubscribe link. See our privacy policy.
Example result
Illustrative example; not tested on the listed platform. Inputs are fictional and contain no private customer data.
How to use this prompt
- 101 Choose a tool: compare the fit. 02 Use a prompt: start with context. 03 Check the result: keep your judgment.
- 2Restrict the review to an authorized repository and use a safe local fixture.
- 3Ask for evidence and unknowns before accepting a severity rating.
- 4Inspect the patch and run the regression test yourself if the platform cannot execute it.
- 5Check the result: Each trace identifies a real supplied line and the prerequisites for the failure.
- 6Check the result: CWE labels and severity have a rationale; hypotheses remain labelled.
- 7Check the result: Actual tests pass after the minimal patch without unrelated changes.
Tips & limitations
Recommended model: gemini-4-argon. Open the listed platform, then select the available model yourself; this page does not run it. Illustrative example; not tested on the listed platform. Current topic selection is based on official releases and concrete reader tasks. No measured trend ranking or search-volume claim.
Did this help you complete your task?
Tell us what needs improving. No account or private output required.
Report incorrect information or a broken linkReview evidence
Documentation-based review · 2026-10-14
Recommended model: gemini-4-argon. Open the listed platform, then select the available model yourself; this page does not run it. Illustrative example; not tested on the listed platform. Current topic selection is based on official releases and concrete reader tasks. No measured trend ranking or search-volume claim.