メニュー
Fetch a Jira ticket via the Atlassian MCP and summarize its intent and acceptance criteria. Use when: reading a Jira ticket, pulling ticket context, looking up a ticket's details, getting acceptance criteria. Building block for other skills that need ticket context.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Scaffold a web repo with pnpm, Astro, and astro-bulma — plus Drizzle when the site needs a database — including package.json scripts for build/lint/test/fmt (and db:migrate when db-backed). Use when: setting up a new Astro project, scaffolding a web repo, initializing the standard web stack. Building block for create-website.
Add a GitHub Actions CI workflow running build, lint, test, and fmt checks with pnpm. Use when: adding CI, setting up GitHub Actions checks, adding a build/lint/test workflow. Building block for create-website.
Create a new website end-to-end: Astro repo with pnpm/astro-bulma; GitHub Pages for static sites, or Turso + Fly.io when the site needs a database; GitHub Actions for CI and deploy. Use when: creating a new website, spinning up a new web project, new site, scaffolding a static or full-stack Astro project.
Create a new app on Fly.io for the current project without deploying it, generating fly.toml and a Dockerfile. Use when: creating a Fly.io app, setting up Fly hosting, fly launch. Building block for create-website.
Add a GitHub Actions workflow that builds a static site and deploys it to GitHub Pages, with an optional custom domain. Use when: deploying a static site, GitHub Pages hosting, static site with a custom domain. Building block for create-website.
Add a GitHub Actions workflow that deploys to Fly.io on merge to main, with db migrations run as a Fly release_command. Use when: adding a deploy workflow, deploying on merge, setting up continuous deployment to Fly.io. Building block for create-website.
| name | jira-read-ticket |
| description | Fetch a Jira ticket via the Atlassian MCP and summarize its intent and acceptance criteria. Use when: reading a Jira ticket, pulling ticket context, looking up a ticket's details, getting acceptance criteria. Building block for other skills that need ticket context. |
| argument-hint | Jira ticket key (e.g. DT-1234), or text/branch/PR to extract one from |
Fetch a Jira ticket and produce a concise, structured summary of its intent. This is a building block — other skills call it whenever they need ticket context.
Find a Jira key (e.g. DT-1234, PROJ-567 — typically uppercase letters, a hyphen, and digits) from, in order of preference:
If no key is found, report that no ticket could be identified and stop — let the caller decide how to proceed (ask the user, fall back to other context, etc.). Do not invent or guess a key.
Retrieve the full issue with the getJiraIssue MCP tool. Capture:
If the fetch fails (no access, bad key), report that clearly rather than fabricating details.
Output a brief, structured summary the caller can use directly:
**<KEY>: <summary>** (<status>)
<2–4 sentence plain-English description of the goal>
**Acceptance criteria:**
- <criterion> (or "none stated")
**Notes:** <constraints, dependencies, linked tickets — omit if none>
Keep it tight. The point is shared, reliable ticket context, not a transcript of the ticket.