What problem does it solve?
After a Codex Security scan produces validated findings, teams still need to file them into issue trackers without losing accuracy, creating duplicates, or leaking sensitive details. This Skill turns sealed scan results into reviewed, approval-gated Linear issues, Jira issues, GitHub issues, or draft GitHub security advisories.
Core Features & Use Cases
- Multi-provider tracking: Create, reuse, or update findings in Linear, Jira Cloud (via Atlassian Rovo), GitHub issues, or private draft GitHub security advisories, using one provider and destination per run.
- Duplicate detection and binding: Searches by canonical finding id and fingerprint before any write, choosing create, reuse, update, or blocked outcomes per finding.
- Approval-gated writes with readback: Shows the exact payload for review, rechecks source and destination after approval, executes serially, and verifies every write through provider readback.
- Use Case: After a sealed scan reports 12 validated findings, select a batch, preview the exact Jira issues with commit-pinned source links, approve once, and get verified issue URLs back.
Quick Start
Track the validated findings from my latest Codex Security scan as GitHub issues in the scanned repository, showing me a preview before writing anything.