Assess Findings

Turn an observed finding into a supported judgment and a useful next-action recommendation. Assess the finding's basis separately from the value of a proposed response. A worthwhile optional improvement can justify a PR without being necessary; reproducibility alone establishes behavior, not a defect.

If the user supplies only a PR, recover the finding from its stated purpose and linked records. Assess its impact, the proposed response and coverage of the original outcome. Select checks, delegated work and evidence from existing records by the same question: can this fact change the judgment about the original finding? State the remaining gap against that finding’s acceptance conditions. Leave other recorded defects and their repair decisions in their own records. A patch review or merge verdict requires a separate request.

Use investigate-with-evidence for factual uncertainties that could change the judgment. Install both skills together. This workflow authorizes analysis and bounded investigation within the consuming task's permissions; repair and publication remain separate actions.

English output

simple-english is optional. If it is installed and readable, use it when writing or revising English prose. Reuse instructions already loaded. If it is unavailable, write clear English and complete the task normally. Its absence does not require installation, an exception, or draft-only delivery.

Preserve meaning, uncertainty, requirement strength, domain terms, and requested formats when style rules conflict. Keep the requested language. Preserve code, identifiers, commands, original quotations, and historical evidence.