Git workflow (week one)

How Team Rephrased engineers branch, review, and merge. Use this page before your first pull request.

Weekly rhythm

1. Pull latest main before starting new work.
2. Create a task branch from main.
3. Work in Unreal, C++, Blueprints, or wiki Markdown on that branch.
4. Test the affected gameplay, level, or docs path (PIE on Rune Showcase or your assigned level).
5. Tell your coding agent (Cursor, Claude Code, Codex, Antigravity, or another MCP-capable IDE) you are done / want to commit (see Self-review workflow). You compile and PIE.
6. Open a PR into main with summary, test steps, risk, and ownership impact.
7. Lead review before merge.

Branch naming

Pattern: <category>/<area-or-level>-<short-task>

Category	Use for
feature/	New gameplay, levels, systems, or docs
bugfix/	Defect fixes
docs/	Wiki or repo documentation only
chore/	Tooling, hooks, non-gameplay maintenance
experiment/	Spikes that may not merge

Examples:

• feature/level1-first-rune-puzzle
• feature/rune-verb-noun-grammar
• bugfix/rune-slot-hover-flicker
• docs/engineer-onboarding
• chore/install-review-hook

Pull request checklist

Before you open the PR:

• [ ] Branch is up to date with main (rebase or merge as your lead prefers).
• [ ] Project compiles (Development Editor | Win64 for engineers).
• [ ] You PIE-tested the change (or documented why not).
• [ ] You told your coding agent to finish the review gate (or noted why not).
• [ ] Wiki edits under Rephrased Wiki/ have ## Change history entries.
• [ ] A devlog exists if the session was substantial.

PR description: include Summary, Test plan, and Risk / rollback.

Devlogs

• Weekly per-engineer logs: devlogs/README.md
• Engineering lead chronological log: DEVLOG.md

Write a devlog when you finish a feature slice, fix a blocking bug, or change onboarding/docs that teammates rely on.

Related pages

• First day (engineering) — setup and weekly workflow
• Today is your first day — shared install
• Self-review workflow — coding-agent review before push
• Wiki maintenance — metadata and change history on doc edits

Change history

• 2026-08-14 — Gabriel Li — Related link is First day (engineering) only. Review-gate wording lists all team coding-agent harnesses.
• 2026-08-13 — Gabriel Li — PR checklist uses MCP review gate language; dropped named-skill steps.
• 2026-05-23 — Gabriel Li — Week-one Git/PR workflow published from onboarding audit follow-up.