pr-workflow

# PR Workflow Complete workflow for taking local code changes through branch creation, PR, CI verification, failure fix, and merge. ## Prerequisites - Code changes are already made and tested locally - Remote `origin` is configured - `gh` CLI is authenticated ## Steps ### 1. Pre-flight Check ```bash git status git diff --stat git log --oneline -5 ``` Verify before proceeding: - Only intended files are modified - No sensitive files (.env, credentials) staged - No temp artifacts (screenshots, logs) left behind ### 2. Create Branch Branch from current HEAD. Naming convention: | Type | Prefix | Example | |------|--------|---------| | Bug fix | `fix/` | `fix/remove-legacy-textarea` | | Feature | `feat/` | `feat/structured-ac-editor` | | Refactor | `refactor/` | `refactor/service-layer` | | Test | `test/` | `test/e2e-proposal-flow` | | Docs | `docs/` | `docs/api-reference` | | Chore | `chore/` | `chore/bump-deps` | ```bash git checkout -b {prefix}{short-description} ``` ### 3. Stage and Commit Stage specific files only — never use `git add .` or `git add -A`: ```bash git add path/to/file1 path/to/file2 ``` **Note**: Next.js paths need shell escaping: ```bash git add src/app/\(dashboard\)/projects/\[uuid\]/file.tsx ``` Commit with HEREDOC for clean multi-line messages: ```bash git commit -m "$(cat <<'EOF' {type}: {concise description of why, not what} {Optional body explaining context or trade-offs} Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.c...