Skill: Report Analyzer Issue

Turn a confirmed engine-level diagnosis into a self-contained .opentaint/issues/<slug>.md report, and optionally a GitHub issue. It only writes the report from the diagnosis, the test project, and the rule or approximation it concerns — it runs no analysis of its own

Inputs

From the caller; if omitted, fall back to the default. Ask only when a required input is missing and has no sensible default

• Diagnosis <diagnosis> — debug-rule's engine-level conclusion: where taint dies (file:line + instruction), the fact-reachability trace up to the last reachable fact, and observed vs expected verdict
• Test project <test-project> / <test-compiled> — the project the artifact was tested on and debug-rule traced, already built by create-test-project. Default: .opentaint/test-projects/<name> / .opentaint/test-compiled/<name>
• Artifact <artifact> — the rule or approximation the issue concerns: a rule's full id and ruleset, or the approximation's target method(s)
• Issue file <issue-file> — where to write the report. Default: .opentaint/issues/<slug>.md; <slug> is a short kebab-case symptom name (a filename — no spaces or hashes)
• Open a GitHub issue <open-issue> (optional) — whether to also file at github.com/seqra/opentaint; the main agent decides and passes this. Default: no

Workflow

1. Gate — require an engine diagnosis

File a report only for an engine issue debug-rule already confirmed. The diagnosis must establish all three; if any is missing, return to the caller and ask for debugging first — don't verify or run anything yourself: