Skill: Report Analyzer Issue

Turn a suspected engine-level problem into a self-contained .opentaint/issues/<slug>.md report. It runs no analysis of its own — it only writes the report from what the caller supplies. Two kinds:

• an analysis issue — a suspected engine-level taint-propagation problem the caller couldn't resolve with a rule or a model (the analyzer's result looks wrong)
• a resource issue — a full-project scan that produced no SARIF after its allowed retry, memory bound, or timeout backstop; no taint diagnosis, just the setup that triggered it so the engine team can reproduce

Inputs

Provided by the caller, fall back to the default value when omitted. Ask back only when a required input is missing and has no sensible default

• project-root (optional) — root of the target project. Opentaint keeps all analysis artifacts under the fixed <project-root>/.opentaint/ directory, so every .opentaint/... path below resolves there. Default: current directory
• diagnosis (required for analysis) — the caller's brief engine-level cause: roughly where taint appears to die and why. A short hand-off, not a proven trace
• artifact (required for analysis) — the rule or approximation the issue concerns: a rule's full id and ruleset, or the approximation's target method(s)
• name (optional, analysis) — the test-project name the artifact was traced on; its tree is .opentaint/test-projects/<name> and model .opentaint/test-compiled/<name>, cited so the engine team can reproduce
• setup (required for resource) — what was running when the scan failed without SARIF: the ruleset(s), approximation dirs, project model, final memory bound, timeout/backstop outcome, scan log, and commit hash (git rev-parse HEAD)

Workflow