Skip to content

Working without an AI agent

Everything below works without Codex, Claude Code, Cursor, or any AI tool. The AI toolchain is optional — the repo itself guards the workflow (git hooks + PR checks), so a manual engineer is fully covered.

Daily loop

  1. Pull latest main: 
    git pull
  2. Build once per day with the helper: 
    .\[OpenAfterPull]Build_Project.bat -check
    then run the bat normally and open the Rune Showcase level.
  3. Create a task branch (never work on main): 
    git checkout -b feature/<area>-<task>
    Name it <category>/<area-or-level>-<short-task> with one of: feature/, fix/, bugfix/, docs/, chore/, refactor/, test/, experiment/. The repo's git hooks automatically block commits/pushes on main/master, detached HEAD, and badly named branches — this works for manual engineers too, no setup needed.
  4. Commit on your branch: 
    git add <files>
git commit
  5. Push and open a PR into main: 
    git push -u origin <branch>
    Use the PR template (summary, linked ticket, what changed/why, verification evidence, review checklist, rollback notes, video/screenshot when relevant). GitHub validates the template sections automatically.

Reviews without an agent

  • convention_check (MCP-only): self-check your C++ against the coding conventions before committing: ASCII-only UE_LOG, no banner comments, actor ids via GetActorNameOrLabel(), include order (own header → engine → project → third-party), no unused placeholder blocks.
  • Team review (request_review, MCP-only): ask your lead or a teammate with an agent to run the review pass on your branch before merging. A human reviews the PR regardless.
  • Compile + PIE: always yours — build in VS and playtest before opening the PR.

Devlog without an agent

Write the weekly entry by hand, following the devlogs README: one ## YYYY-MM-DD section per day, with a one-line summary, files touched, decisions/blockers, and the team task link if any. File lives at Rephrased Wiki/wiki/devlogs/YYYY-Www-<your-name>.md. Or ask a teammate with an agent to draft it via the devlog tool.

Keys and MCP

Not needed. The review key (rephr_...) only gates the agent-side tools. If you start using Codex / Claude Code / Cursor later, follow the two-phase "onboard me" flow in MCP setup — no manual config.

Change history

  • 2026-08-27 - Gabriel Li - Created manual workflow page so engineers without AI agents have a documented path.