メニュー
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".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when creating, updating, or compacting Architecture Decision Records (ADRs). Use when user says "adr", "crear ADR", "create ADR", "actualizar ADR", "update ADR", "compactar ADR", "compact ADR", "registrar decision", "record decision", "decision record".
Use when needing to query a PostgreSQL database in DEV or PROD, check if records exist, count rows, inspect data, or run read-only SQL queries from within the cluster. Use when user says "consulta la BD", "query", "busca en la tabla", "check database", "db query", or "existe este registro".
Use when user asks to deploy to production, check what's deployed, find a docker image tag for a PR, or trigger a production deployment. Use when user mentions "deploy", "prod", "production", "release", or "ship".
Use when checking pod logs, searching for errors, viewing recent log output, or debugging runtime issues in DEV or PROD. Use when user says "logs de", "ver logs", "qué errores hay", "check logs", "show errors", or mentions log analysis of a service.
Use when user asks to run database migrations, create tables, apply schema changes, or mentions "migration" in the context of DEV or PROD environments. Use when user mentions "migrate", "migration:up", "create table", or "schema changes" for remote environments.
Use when checking pod status, listing running services, investigating crashloops, viewing pod events, or checking resource usage. Use when user says "pods", "qué está corriendo", "pod status", "check pods", "restart", "crashloop", or "pod events".
| name | jira-create-bug |
| description | 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". |
| argument-hint | [brief description] |
| allowed-tools | AskUserQuestion, ToolSearch, mcp__claude_ai_Atlassian__searchJiraIssuesUsingJql, mcp__claude_ai_Atlassian__lookupJiraAccountId, mcp__claude_ai_Atlassian__createJiraIssue, mcp__claude_ai_Atlassian__editJiraIssue |
| model | sonnet |
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.
Search for epics in DEVPT project:
JQL: project = DEVPT AND issuetype = Epic AND (summary ~ "<keyword>") ORDER BY updated DESC
Common epics:
If unsure which epic, ask the user or default to DEVPT-25.
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.>
Use the Atlassian MCP tools:
searchJiraIssuesUsingJql — Find the right epiclookupJiraAccountId — Find the assignee's account IDcreateJiraIssue — Create with:
projectKey: "DEVPT"issueTypeName: "Bug"summary: Concise, includes service name and what's brokendescription: Structured markdown (template above)parent: Epic key (e.g., "DEVPT-25")editJiraIssue — Assign to the userGood summaries:
backoffice-api: DTO de jiraRefs requiere summary y status como obligatorios, causando rechazo de mensajes en DLQobligations-api: provided-service subscriber falla por campo faltante en erpRefBad summaries:
Bug en el servicio (too vague)Error (useless)Format: <service>: <what's broken and visible effect>