Menu
Transition a Jira issue to a new status using MCP tools. Use when: moving a ticket to In Progress, In Code Review, Done, or any other status.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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-transition |
| description | Transition a Jira issue to a new status using MCP tools. Use when: moving a ticket to In Progress, In Code Review, Done, or any other status. |
| argument-hint | Jira ticket (e.g. DT-1234) and target status (e.g. "In Code Review") |
lane/<TICKET>-<slug>), or ask the user.getJiraIssue — if the issue is unassigned, assign it to the current user:
atlassianUserInfo.editJiraIssue to set the assignee to that account ID.getTransitionsForJiraIssue to fetch available transitions for the ticket.transitionJiraIssue with the matching transition ID.If Jira MCP tools are unavailable, remind the user to move the ticket manually.