Skill: OpenTaint Issue Investigation

Investigate and confirm an issue in the OpenTaint analysis engine — a case where a rule that should fire does not (or fires where it should not), and the cause is not the rule's syntax or the library modeling, but the engine itself (e.g. an intra/inter-procedural dataflow path that is cut unexpectedly).

The deliverable is a small, self-contained reproducer plus a short write-up that points at the exact instruction where the dataflow dies.

When to use this skill

Use it after analyze-findings / create-yaml-config / create-approximation have been exhausted and a finding is still missing (or spurious), even though:

• The rule passes its own tests on isolated samples.
• external-methods-without-rules.yaml is empty (or irrelevant) for the relevant code path.
• Nothing about the library model is obviously wrong.