jira-read-ticket

Estrelas11

Forks2

Atualizado2 de agosto de 2026 às 10:04

Use whenever a user mentions or references a Jira ticket and you want to pull out description, comments, or more.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

bkircher

bkircher/skills

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Outras ocupações de informáticaInformática e Matemática·SOC 15-1299

Explorador de arquivos

6 arquivos

SKILL.md

readonly

name	jira-read-ticket
description	Use whenever a user mentions or references a Jira ticket and you want to pull out description, comments, or more.

Jira data access instructions

Retrieve Jira issue data from Atlassian Cloud and return only the requested fields in JSON format.

Inputs

Jira issue key or ticket URL
Environment variables: ATLASSIAN_URL, ATLASSIAN_EMAIL, ATLASSIAN_API_TOKEN

Workflow

1) Verify environment variables

Ensure all required variables are set. Never output or log token values.
If missing, ask the user to set them before calling the API.

Variables: ATLASSIAN_URL, ATLASSIAN_EMAIL, ATLASSIAN_API_TOKEN

2) Identify the issue key

If the user provides a URL, parse the key (example: https://.../browse/ABC-123 -> ABC-123).
If the key is missing, ask the user for it.

3) Fetch data

Use these scripts before alternatives:

scripts/fetch_comments.py: Gets all ticket comments as JSON.
scripts/fetch_assigned_tickets.py: Gets assigned tickets (JSON array).
scripts/fetch_description.py: Gets description and details for one ticket (JSON).

Alternatively, use Jira REST API v3 with basic authentication, curl, and jq. Example for assigned tickets with JQL:

curl -s \
  -u "$ATLASSIAN_EMAIL:$ATLASSIAN_API_TOKEN" \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  "$ATLASSIAN_URL/rest/api/3/search/jql" \
  --data '{
    "jql": "assignee = currentUser()",
    "fields": ["key", "summary", "status", "issuetype", "project"],
    "maxResults": 100
  }'

Use the fields parameter to limit payload when only specific fields are needed.

4) Extract results

Python scripts return JSON.
When using curl, use jq to extract fields of interest.

Notes

Jira may return rich text (Atlassian Document Format). Prefer renderedFields, fallback to fields.
Use /rest/api/3/search/jql for JQL POST requests. /rest/api/3/search is deprecated.
Retry API requests with increased permissions if network restrictions occur.
Never log or output secrets—reference environment variable names only.
Read-only operation: do not alter ticket data unless explicitly authorized by the user.

Mais deste repositório

mesmo repositório

unit-testing

bkircher/skills

Use when writing or updating unit tests (in any language).

2026-08-0211

git-commit-message

bkircher/skills

Generate Git commit messages from staged changes when requested.

2026-07-2611

snyk-cli

bkircher/skills

Scan and triage Snyk security findings in local repositories and container images. Use for Snyk vulnerability reviews, scan summaries, severity filtering, and remediation planning.

2026-07-1611

sonar-cli

bkircher/skills

Use the SonarQube CLI to access and understand SonarQube analysis results. Use when the user asks about SonarQube issues.

2026-07-1011

english-text-editor

bkircher/skills

Suggests improvements for English-language text but does not rewrite the original. Use when asked to correct spelling or wording and the text is English.

2026-06-2711

gh-code-review

bkircher/skills

Review GitHub pull requests using gh CLI and the GitHub API. Use when asked to review a PR, inspect PR changes, or choose approve/comment/request-changes.

2026-05-1311

name	jira-read-ticket
description	Use whenever a user mentions or references a Jira ticket and you want to pull out description, comments, or more.

Jira data access instructions

Retrieve Jira issue data from Atlassian Cloud and return only the requested fields in JSON format.

Inputs

Jira issue key or ticket URL
Environment variables: ATLASSIAN_URL, ATLASSIAN_EMAIL, ATLASSIAN_API_TOKEN

Workflow

1) Verify environment variables

Ensure all required variables are set. Never output or log token values.
If missing, ask the user to set them before calling the API.

Variables: ATLASSIAN_URL, ATLASSIAN_EMAIL, ATLASSIAN_API_TOKEN

2) Identify the issue key

If the user provides a URL, parse the key (example: https://.../browse/ABC-123 -> ABC-123).
If the key is missing, ask the user for it.

3) Fetch data

Use these scripts before alternatives:

scripts/fetch_comments.py: Gets all ticket comments as JSON.
scripts/fetch_assigned_tickets.py: Gets assigned tickets (JSON array).
scripts/fetch_description.py: Gets description and details for one ticket (JSON).

Alternatively, use Jira REST API v3 with basic authentication, curl, and jq. Example for assigned tickets with JQL:

curl -s \
  -u "$ATLASSIAN_EMAIL:$ATLASSIAN_API_TOKEN" \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  "$ATLASSIAN_URL/rest/api/3/search/jql" \
  --data '{
    "jql": "assignee = currentUser()",
    "fields": ["key", "summary", "status", "issuetype", "project"],
    "maxResults": 100
  }'

Use the fields parameter to limit payload when only specific fields are needed.

4) Extract results

Python scripts return JSON.
When using curl, use jq to extract fields of interest.

Notes

Jira may return rich text (Atlassian Document Format). Prefer renderedFields, fallback to fields.
Use /rest/api/3/search/jql for JQL POST requests. /rest/api/3/search is deprecated.
Retry API requests with increased permissions if network restrictions occur.
Never log or output secrets—reference environment variable names only.
Read-only operation: do not alter ticket data unless explicitly authorized by the user.