Results for “beweisfragen”

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, ensuring evidence precedes any success claims.

Deliberative consultation with Codex CLI. Ask, evaluate, critique, iterate until workable agreement.

Validate user claims against codebase and git history, trace to root cause, and propose a fix

Verify that a change really works before you claim completion

Require fresh evidence before claiming an implementation, fix, build, or test is complete.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Clarify requirements before implementing by asking targeted questions when a request has multiple plausible interpretations or key details are unclear.

Provides expert guidance for testing Spring Boot 4 applications with modern patterns, test slices, and best practices.

TextVQA: Towards Reasoning about Text in Images

Enforces a verification gate before any completion claim, requiring fresh command output as evidence.

Verify code changes work by running them. Proves through execution, not just inspection.

Deliberative consultation with Gemini CLI. Ask, evaluate, critique, iterate until workable agreement.

Big Data Based Testing Skill

Deliberative consultation with Codex CLI. Ask, evaluate, critique, iterate until workable agreement.

Design and evaluate A/B tests with power, sample size, and robust metric interpretation. Use when: (1) planning controlled experiments, (2) reading p-values/effects, (3) sequential testing safeguards. NOT for: dark-pattern optimization.

Review a code change for changed behavior that could regress without reliable verification catching it. Use when checking whether a change is adequately verified.

Answers questions about a codebase by searching and reading source files, then synthesizing answers with inline citations and a key files table.

The single most useful question before analysing anything is: *what does it cost

Runs an interactive QA session, clarifying user-reported problems, exploring the codebase for context, and filing durable, user-focused GitHub issues.

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, to prevent false success claims.