Menu
Branch naming, commit messages, and PR process for this project
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional 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
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.
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.
| name | git-workflow |
| description | Branch naming, commit messages, and PR process for this project |
Keep history clean and every change traceable: branch by type, commit in the imperative, gate the merge on green CI, and squash to a single readable commit on the way into main.
{type}/{short-kebab-description}
| Type | When |
|---|---|
feat | New feature |
fix | Bug fix |
chore | Maintenance, dependency updates |
refactor | Code restructure, no behavior change |
docs | Documentation only |
test | Tests only |
ci | CI/CD pipeline changes |
Examples:
feat/stripe-subscription-cancel
fix/auth-redirect-loop
chore/update-prisma-6
refactor/dashboard-extract-chart
docs/feature-architecture
test/subscription-action-coverage
ci/add-sonarcloud-step
Format: type(scope): description in imperative mood
feat(auth): add Google OAuth sign-in
fix(stripe): handle webhook signature verification failure
chore(deps): update Prisma to 6.x
test(actions): add cancelSubscription action tests
refactor(dashboard): extract ChartAreaInteractive to component
docs(ci): update Drone pipeline configuration
ci(github): add SonarCloud quality gate step
Valid scopes: auth, stripe, dashboard, i18n, email, db, api, ci, deps, middleware
1. Branch from main
2. Implement with tests (TDD — see rules/testing.md)
3. Run pre-push checks (see below)
4. Open PR with description + issue link
5. Address review comments (see skills/address-pr-comment.md)
6. Squash merge after approval
bun run lint # Biome — lint + format check
bun tsc # TypeScript strict check
bun run test # Vitest — all tests
bun run locale-check # Validate i18n key parity
bun run locale-unused # Detect orphan i18n keys
All checks must pass before pushing — CI runs the same gates and will block the merge otherwise.
# Start feature
git checkout main && git pull origin main
git checkout -b feat/my-feature
# Stage interactively (never `git add .`)
git add -p
# Commit
git commit -m "feat(auth): add email verification flow"
# Sync with main (prefer rebase over merge)
git fetch origin
git rebase origin/main
# Push
git push origin feat/my-feature
# Amend last commit (before push only)
git commit --amend --no-edit
| Branch type | Strategy |
|---|---|
| Feature → main | Squash merge (clean linear history) |
| Release → main | Merge commit |
| Hotfix → main | Squash merge |
main