testland/bug-tracker-workflow
Files, transitions, and searches bugs in the team's tracker - Jira, Linear, GitHub Issues, or Azure DevOps - through one tracker-agnostic workflow: authenticate, dedupe-search before creating, create with severity/priority classification, transition lifecycle states, and wire idempotent CI-driven filing from test failures. Jira Cloud REST API v3 is worked in full in the body (ADF descriptions, runtime transition lookup, JQL triage and duplicate queries, dry-run bulk transitions); Linear's GraphQL API (issueCreate/issueUpdate, workflowStates resolved by type, the 0-4 priority enum), GitHub Issues REST (open/closed + state_reason, label-based severity/priority), and Azure DevOps Work Item Tracking (JSON Patch, WIQL, process-template states) each have a deep reference. Use when programmatically managing the bug lifecycle on any of the four trackers: creating from CI failures, triaging queues, transitioning states, or dedupe-searching.
73
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
SKILL.md and the tracker deep-dives describe CI-driven “file bug on test failure” where the workflow parses free-form JUnit XML (`results.xml`) and then runs dedupe/search and creates/comments on Jira/Linear/GitHub/Azure DevOps, meaning outsider-authored test output can be ingested at runtime without selecting a specific pre-declared item.
Where we found it
JUnit XML (results.xml)
content-type · 7 sites
The plugin ingests free-form JUnit XML test output (results.xml) produced by test runners across four CI integration points (Jira, Linear, GitHub Issues, Azure DevOps), parsing failure messages and forwarding them into bug tracker issue titles, descriptions, and comments — outsider-authored test output (e.g., from PR contributors) can inject content into these tracker entries.
- Audited
- Security analysis