CtrlK
BlogDocsLog inGet started
Tessl Logo

report-bug

Draft and submit a well-specified Jira bug report after explicit confirmation. Use when a user wants to report, file, log, or open a bug rather than fix it now.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Report Bug

Create a truthful, reproducible report useful to triage and a bug-fixing agent.

  1. Resolve the target and template with configuration.md, select capabilities with jira-integration.md, and read bug-report-contract.md.
  2. Gather evidence from the conversation and user-approved local sources. Ask only for material gaps; never invent observations, impact, or severity.
  3. Search Jira read-only for likely duplicates and resolved predecessors. Show candidates and offer to add evidence to a matching open issue when supported.
  4. Draft the new issue or matching-issue evidence comment and its optional fields.
  5. For user-requested or offered attachments, follow references/attachments.md.
  6. Run the applicable quality gate, then preview the target, action, content, fields, and attachment manifest. For a new issue, Priority remains unset.
  7. Wait for explicit confirmation; approval of a draft is not approval to create.
  8. Once confirmed, follow references/jira-creation.md.
  9. Return the issue key and URL, or the exact failure without retrying an uncertain write. This skill is attended by design; do not diagnose or fix.
Repository
flightctl/ai-workflows
Last updated
First committed

Also appears in

amir-yogev-gh/ai-workflows
In sync

since Sep 19, 2026

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.