菜单
Open a pull request for the current branch in ignite-starter using the repository PR template. Use whenever the user asks to open, create, or raise a PR / pull request, or to prepare a branch for review. Runs the verification gate, writes a Conventional Commit, and fills the template.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guides Stripe integration decisions across API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatic_tax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, restricted keys, webhooks, OAuth). Use when building, modifying, or reviewing any Stripe integration, including accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, collecting sales tax, VAT, or GST, creating connected accounts, or implementing secure key handling.
Process PR comments systematically—read all, categorize, fix blocking items, batch changes, reply to threads, and re-review
Branch naming, commit messages, and PR process for this project
Security checklist for code review—validates auth, input validation, secrets, database safety, Stripe integration, XSS prevention, and dependencies
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
Architecture patterns for Next.js 16 App Router apps. Use when scaffolding a new app, adding a feature, refactoring code into feature folders, deciding where queries/actions/components live, placing Suspense boundaries, choosing the client/server boundary, designing skeletons, preventing CLS, or enabling Cache Components. Also use when the user asks about RSC composition, `params.then()`, `'use cache'`, `cacheTag`, `updateTag`, or static-shell prerendering.
| name | open-pr |
| description | Open a pull request for the current branch in ignite-starter using the repository PR template. Use whenever the user asks to open, create, or raise a PR / pull request, or to prepare a branch for review. Runs the verification gate, writes a Conventional Commit, and fills the template. |
You open pull requests for the ignite-starter monorepo. Always pass the verification gate first, write history with Conventional Commits, and describe the change with the repository template — never invent your own PR format.
Inspect the change.
git status
git diff --stat $(git merge-base HEAD origin/main)..HEAD
Run the mandatory gate (from the repo root) and fix anything it flags before continuing:
bun run format
bun run lint
bun run tsc
bun run test
Commit with Conventional Commits. Header ≤ 88 chars, allowed types: build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test.
git commit -m "feat(auth): add password reset flow"
Push and open the PR with the body filled from .github/PULL_REQUEST_TEMPLATE.md:
git push -u origin HEAD
gh pr create --title "feat(auth): add password reset flow" --body-file <filled-template>
Fill this exactly. Remove the Considerations and Screenshots sections when they do not apply.
# Reference
[Add any relevant link (issue, ticket, doc, etc)]
## Changes
- **Added:**
- ...
- **Updated:**
- ...
- **Fixed:**
- ...
## Considerations
[Any considerations about the code changes (remove section if not used)]
## Screenshots
[Any screenshots of changes (remove if not applied)]
@repo/api was regenerated and note it under Considerations.