Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

fd-read-jira-task

Estrellas4

Forks0

Actualizado23 de mayo de 2026 a las 17:03

Reads a Jira task and all linked issues, returning a structured summary including title, description, acceptance criteria, comments, linked epics, and sub-tasks. Use at the start of every planning session.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

fluentdata-ai

fluentdata-ai/zil

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	fd-read-jira-task
description	Reads a Jira task and all linked issues, returning a structured summary including title, description, acceptance criteria, comments, linked epics, and sub-tasks. Use at the start of every planning session.
license	Apache-2.0

fd-read-jira-task

Overview

Use this skill to fully understand a Jira task before planning or implementing anything. It ensures you gather all relevant context including linked issues, comments, and acceptance criteria.

Steps

Use the get_issue MCP tool to fetch the issue by key.
Extract: summary, description, issue type, priority, status, assignee.
Check the description field for acceptance criteria sections.
Use search_issues with a JQL like issue in linkedIssues("KEY") to fetch linked issues if needed.
Return a structured summary with all extracted information.

Notes

If the Jira MCP tool is unavailable, report the error and proceed with only the issue key as context.
Do not modify the Jira issue — this is a read-only skill.

Más de este repositorio

mismo repositorio

get-forecast

fluentdata-ai/zil

Return a concise weather forecast for a given location and (optional) date, including a one-line piece of practical advice. This is the skill the trip-planner agent invokes over A2A.

2026-06-094

fd-submit-changes

fluentdata-ai/zil

Creates a feature branch, stages all changes, commits with a conventional commit message, pushes the branch, and opens a GitHub pull request. Use at the end of every implementation task after all tests pass.

2026-05-294

fd-explore-repo

fluentdata-ai/zil

Systematic repository exploration procedure. Lists directory trees, reads key files (README, pyproject.toml, package.json, etc.), and produces a structured summary of the codebase layout. Use before planning any implementation task.

2026-05-234

fd-format-code

fluentdata-ai/zil

Runs the project's code formatter and linter (ruff, black, isort, etc.) and reports any remaining issues. Use before committing to ensure code style compliance.

2026-05-234

fd-run-tests

fluentdata-ai/zil

Runs the project's test suite and reports pass/fail results. Detects the test framework from the project config and runs the appropriate command. Use after every implementation change before submitting.

2026-05-234

name	fd-read-jira-task
description	Reads a Jira task and all linked issues, returning a structured summary including title, description, acceptance criteria, comments, linked epics, and sub-tasks. Use at the start of every planning session.
license	Apache-2.0

fd-read-jira-task

Overview

Use this skill to fully understand a Jira task before planning or implementing anything. It ensures you gather all relevant context including linked issues, comments, and acceptance criteria.

Steps

Use the get_issue MCP tool to fetch the issue by key.
Extract: summary, description, issue type, priority, status, assignee.
Check the description field for acceptance criteria sections.
Use search_issues with a JQL like issue in linkedIssues("KEY") to fetch linked issues if needed.
Return a structured summary with all extracted information.

Notes

If the Jira MCP tool is unavailable, report the error and proceed with only the issue key as context.
Do not modify the Jira issue — this is a read-only skill.