swarm-ticket-drafter

You can convert approved audit findings into GitHub issues automatically by providing the findings list to an automation workflow that formats each finding into a standardized ticket with proper labels on your target repository.

The best way to avoid duplicate GitHub issues from audit reports is to apply deduplication checks against existing open issues before batch creation, ensuring only new, unique findings are formatted and posted as tracked tickets.

Yes, you can batch create GitHub issues from a findings list with partial-failure tolerance. The workflow processes approved findings individually, continuing ticket creation even if some requests fail, and generates a final report of successes and failures.

To apply approval gating before generating GitHub tickets, you must provide an explicitly approved findings list. The ticket creation workflow only triggers when findings have passed your internal review, ensuring accountability before issues are drafted.

Yes, the ticket drafter workflow supports standardized issue body templating for audit reports. It formats each approved finding into a consistent GitHub issue structure with appropriate labels, ensuring uniform tracking across all generated tickets.

When new audit findings are processed, the workflow performs deduplication checks against existing open GitHub issues. If a finding matches an existing issue, it skips creation to prevent duplicates; otherwise, it formats and creates a new tracked ticket.