How do I install the Jira Create Bug skill?

Run npx skillmds@latest add weorbitant/jira-create-bug in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Jira Create Bug safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Jira Create Bug?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Jira Create Bug free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Jira Create Bug?

weorbitant (@weorbitant) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Jira Create Bug by weorbitant — Agent Skill

Name: Jira Create Bug
Author: weorbitant

Jira Create Bug

Use when creating a bug report in Jira, reporting an issue found during development or operations, or filing a ticket for a production problem. Use when user says "crea un bug", "reporta bug", "create bug", "file a bug", "abre un ticket", or "report issue".

weorbitant 484b56c 2.4 KB Updated Sep 17, 2026

File contents

Create Jira Bug

Overview

Create well-structured bug reports in Jira with root cause analysis, evidence, and fix recommendations. Uses the DEVPT project and links to the appropriate epic.

Process

Gather information — Understand what the bug is, evidence, and root cause if known
Find the right epic — Search for the relevant epic to link the bug to
Create the bug — With structured description
Assign — Ask user who to assign it to

Finding the Epic

Search for epics in DEVPT project:
JQL: project = DEVPT AND issuetype = Epic AND (summary ~ "<keyword>") ORDER BY updated DESC

Common epics:

DEVPT-25 — "PGI - Bugs, Deuda técnica y mejoras" (catch-all for bugs and tech debt)

If unsure which epic, ask the user or default to DEVPT-25.

Bug Description Template

Use this structure for the description:

## Descripción
<What is happening and what should happen instead>

## Evidencia
- **Entorno**: DEV/PROD
- **Servicio**: <service name>
- <Specific evidence: error messages, message counts, log lines>

## Causa raíz
<Technical explanation of why this is happening>

## Fix requerido
<Specific code change needed, with file paths if known>

## Impacto
<What is affected: messages stuck, data not syncing, users impacted, etc.>

Creating the Bug

Use the Atlassian MCP tools:

searchJiraIssuesUsingJql — Find the right epic
lookupJiraAccountId — Find the assignee's account ID
createJiraIssue — Create with:
- projectKey: "DEVPT"
- issueTypeName: "Bug"
- summary: Concise, includes service name and what's broken
- description: Structured markdown (template above)
- parent: Epic key (e.g., "DEVPT-25")
editJiraIssue — Assign to the user

Summary Guidelines

Good summaries:

backoffice-api: DTO de jiraRefs requiere summary y status como obligatorios, causando rechazo de mensajes en DLQ
obligations-api: provided-service subscriber falla por campo faltante en erpRef

Bad summaries:

Bug en el servicio (too vague)
Error (useless)

Format: <service>: <what's broken and visible effect>

---name: jira-create-bugdescription: Use when creating a bug report in Jira, reporting an issue found during development or operations, or filing a ticket for a production problem. Use when user says "crea un bug", "reporta bug", "create bug", "file a bug", "abre un ticket", or "report issue".---# Create Jira Bug## OverviewCreate well-structured bug reports in Jira with root cause analysis, evidence, and fix recommendations. Uses the DEVPT project and links to the appropriate epic.## Process1. **Gather information** — Understand what the bug is, evidence, and root cause if known2. **Find the right epic** — Search for the relevant epic to link the bug to3. **Create the bug** — With structured description4. **Assign** — Ask user who to assign it to## Finding the Epic```Search for epics in DEVPT project:JQL: project = DEVPT AND issuetype = Epic AND (summary ~ "<keyword>") ORDER BY updated DESC```Common epics:- **DEVPT-25** — "PGI - Bugs, Deuda técnica y mejoras" (catch-all for bugs and tech debt)If unsure which epic, ask the user or default to DEVPT-25.## Bug Description TemplateUse this structure for the description:```markdown## Descripción<What is happening and what should happen instead>## Evidencia- **Entorno**: DEV/PROD- **Servicio**: <service name>- <Specific evidence: error messages, message counts, log lines>## Causa raíz<Technical explanation of why this is happening>## Fix requerido<Specific code change needed, with file paths if known>## Impacto<What is affected: messages stuck, data not syncing, users impacted, etc.>```## Creating the BugUse the Atlassian MCP tools:1. `searchJiraIssuesUsingJql` — Find the right epic2. `lookupJiraAccountId` — Find the assignee's account ID3. `createJiraIssue` — Create with: - `projectKey`: "DEVPT" - `issueTypeName`: "Bug" - `summary`: Concise, includes service name and what's broken - `description`: Structured markdown (template above) - `parent`: Epic key (e.g., "DEVPT-25")4. `editJiraIssue` — Assign to the user## Summary GuidelinesGood summaries:- `backoffice-api: DTO de jiraRefs requiere summary y status como obligatorios, causando rechazo de mensajes en DLQ`- `obligations-api: provided-service subscriber falla por campo faltante en erpRef`Bad summaries:- `Bug en el servicio` (too vague)- `Error` (useless)Format: `<service>: <what's broken and visible effect>`

Frequently asked questions