tools-only Git Workflow
If your project has a
project-implementation.mdrule, check it for framework-specific overrides.
Remotes
Configure remotes in your project's project-implementation.md. Standard setup:
| Remote | URL | Purpose |
|---|---|---|
origin |
Your repository | Primary development |
Branch Strategy
| Branch | Purpose | Pushes To |
|---|---|---|
development |
Active working branch -- all daily work lands here | origin/development |
main |
Stable branch -- CI runs here, deploy candidates | origin/main |
All daily development happens on development. Use PRs from development to main when ready to trigger CI and prepare a release.
Commit Message Format
<type>(<scope>): <description>
<optional body>
| Field | Values |
|---|---|
| type | feat, fix, refactor, docs, test, chore, perf, ci |
| scope | App name or feature area (e.g., auth, dashboard, billing) |
Before Pushing
Run your verification suite as a pre-push gate. Skipping it means broken code reaches origin:
pnpm verify # typecheck + lint + test
If verify fails, fix issues before pushing.
CI Pipeline
Standard CI jobs for Next.js/Supabase projects:
| CI Job | What it does | Timeout |
|---|---|---|
| TypeScript | typecheck + lint |
10 min |
| Unit Tests | pnpm test |
10 min |
| E2E Tests | Playwright (if enabled) | 20 min |
Pull Request Workflow
When creating PRs:
- Analyze full commit history (not just latest commit)
- Use
git diff [base-branch]...HEADto see all changes - Draft comprehensive PR summary
- Include test plan with TODOs
- Push with
-uflag if new branch
Feature Implementation Workflow
- Plan -- Use
/create-planto generate phases and structure (includes/audit-planfor structural checks, then/review-planfor template + codebase compliance) - Implement -- Use
/implementto execute phases (handles TDD, coding, review loop) - Code Review -- Use
/code-reviewafter implementation to verify quality - Verify -- Run
pnpm verifybefore committing - Commit -- Follow conventional commits format with scope