agentleFS
flightctlflightctl/ai-workflows/skills/report-bug/SKILL.md

report-bug

Skill10 starsChanged 21 days agoMITView on GitHub

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.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 11
  2. Distinctive:

    Search Jira read-only for likely duplicates and resolved predecessors.

    line 18
  3. Distinctive:

    Run the applicable quality gate, then preview the target, action, content, fields, and attachment manifest.

    line 23
  4. Distinctive:

    Wait for explicit confirmation.

    line 25

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.