Team SOPs | Warp Training

☀️

SOP: Starting Your Day

Run this every morning before coding

Morning Sync

# 1. Navigate to your project

❯ cd ~/projects/your-project

# 2. Get latest code from main

❯ git checkout main && git pull origin main

# 3. Switch back to your branch & rebase

❯ git checkout your-branch && git rebase main

# 4. Install any new dependencies

❯ npm install

# 5. Start dev server

❯ npm run dev

⚡

Quick Version

Type # morning sync for my project in Warp to get AI help with this workflow.

🆕

SOP: Starting a New Feature

Before writing any code for a new feature

1

Make sure you're on main and up to date

git checkout main && git pull

2

Create a new branch with naming convention

git checkout -b feature/description-here

3

Push branch to remote immediately

git push -u origin feature/description-here

4

Create draft PR on GitHub

This lets the team know what you're working on

📝

Branch Naming Convention

feature/add-user-auth | fix/login-bug | hotfix/critical-issue | chore/update-deps

💾

SOP: Committing Code

Write clear, consistent commit messages

Commit Message Format

❯ git commit -m "type: short description"

# Examples:

feat: add user authentication

fix: resolve login redirect bug

docs: update API documentation

style: format code with prettier

refactor: simplify auth logic

test: add unit tests for login

chore: update dependencies

feat: New feature

fix: Bug fix

docs: Documentation

refactor: Code restructure

test: Adding tests

chore: Maintenance

👀

SOP: Code Review Process

Before merging any PR

1

Self-review first

Look at your own PR diff before requesting review

2

Ensure tests pass

npm run test && npm run lint

3

Request review from at least 1 team member

Use GitHub's reviewer request feature

4

Address all comments

Resolve or respond to every review comment

5

Squash and merge

Use "Squash and merge" to keep history clean

🚀

SOP: Deploying to Production

Checklist before every deploy

✅

All tests passing

npm run test

✅

Build succeeds locally

npm run build

✅

Environment variables set

Check Vercel/hosting dashboard for all required env vars

✅

PR approved and merged to main

Never deploy from feature branches

✅

Notify team in Slack/Discord

"Deploying [feature] to production"

Deploy Commands

# Vercel (auto-deploys on push to main)

❯ git push origin main

# Manual Vercel deploy

❯ vercel --prod

🔥

SOP: Emergency Hotfixes

When production is broken

Hotfix Procedure

# 1. Create hotfix branch from main

❯ git checkout main && git pull

❯ git checkout -b hotfix/describe-issue

# 2. Make the fix

# 3. Test locally

❯ npm run test && npm run build

# 4. Push and create PR

❯ git push -u origin hotfix/describe-issue

# 5. Get quick review & merge immediately

⚠️

Hotfix Rules

Hotfixes skip normal review process but MUST be reviewed by at least one other person. Document the issue in the PR description.

🌙

SOP: End of Day

Before logging off

1

Commit your work-in-progress

git add . && git commit -m "wip: description"

2

Push to remote

git push

3

Update your PR description

Note what's done and what's remaining

4

Post standup update

What you did today, blockers, tomorrow's plan

💡

Never leave uncommitted work

Your laptop could crash overnight. Always push your code, even if it's incomplete. Use "wip:" prefix for work-in-progress.