メニュー
Ship work: validate branch naming (lane/PROJ-###-description), stage changes, craft a conventional commit message, commit, push, and open a GitHub PR using the repo pull_request_template.md. Use when: ship, commit and push, open PR, create pull request, submit work.
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 | ship |
| description | Ship work: validate branch naming (lane/PROJ-###-description), stage changes, craft a conventional commit message, commit, push, and open a GitHub PR using the repo pull_request_template.md. Use when: ship, commit and push, open PR, create pull request, submit work. |
| argument-hint | Optional: Jira ticket (e.g. DT-1234) and/or brief description of the change |
End-to-end workflow: branch → commit → push → PR.
Run git branch --show-current to get the current branch name.
The branch must match: lane/<TICKET>-<slug> or lane/<slug> (no ticket).
main, dev, staging, or another protected/default branch, you must create a new branch. Do not commit to a default branch.
remove-offset-slice, fix-auth-redirect). Do not ask the user for a slug.git checkout -b lane/<TICKET>-<slug> (or lane/<slug> if no ticket)git push origin HEADgit branch -m lane/<TICKET>-<existing-slug>git push origin HEAD --no-verifyRun git status and git diff --stat to understand what's changing. If nothing is staged, run git add -A (ask the user first if the diff is large or contains unexpected files).
Follow the conventional-commit skill.
Follow the github-pr skill.
If a Jira ticket was identified (from the branch name or provided by the user), follow the jira-transition skill targeting "In Code Review".
--force / -f) without explicit user confirmation.--no-verify on the final commit (only on branch renames if needed).