Skip to content

Current Rephrased repo workflow

This page is the source-of-truth workflow note for the post-org Rephrased setup.

Source of truth

Daily team work happens in the GitHub organization:

  • GitHub org: Rephrased-Games
  • Main game repo: Rephrased-Games/Rephrased-Game
  • UE project: Rephrased.uproject
  • Canonical wiki path in the main repo: Rephrased Wiki/
  • Canonical MCP toolkit path in the main repo: tools/rephrased-mcp/

The old demo repo is historical/reference only. Do not clone it for new onboarding, do not start new feature work there, and do not treat it as the current project.

Live wiki deployment

The live wiki URL is currently documented as https://rephrased.zhangzhutian.workers.dev/. Because daily work moved to Rephrased-Games/Rephrased-Game, the Cloudflare Pages/Workers deployment must also build from the org repo, not the old demo repo.

Preferred deployment source:

  • Repository: Rephrased-Games/Rephrased-Game
  • Branch: main
  • Build command: python -m mkdocs build --strict
  • Output directory: site
  • Docs config: root mkdocs.yml, with docs_dir: Rephrased Wiki

Do not change DNS first. First audit the existing Cloudflare project source repo, branch, build command, output directory, and custom domain/route. If Cloudflare cannot reconnect the existing project cleanly, create a new Pages project from the org repo, verify preview build, then swap the custom domain.

The standalone Rephrased-Wiki repo is a reference copy, not the preferred live deployment source unless the team explicitly changes the source-of-truth policy.

Standalone reference repos

Two standalone repos exist for outward reference/showcase:

  • Rephrased-Games/Rephrased-Wiki - reference copy of Rephrased Wiki/
  • Rephrased-Games/Rephrased-agent-toolkit - reference copy of tools/rephrased-mcp/

The main game repo remains canonical. Edit wiki/MCP content in Rephrased-Game first, then sync outward to the standalone repos by branch + PR. Do not make standalone-only edits unless explicitly approved.

Team setup policy

Everyone installs the local toolchain once:

  • Unreal Engine 5.8
  • Visual Studio 2026 Community, stable channel
  • Repo-root .vsconfig imported in Visual Studio Installer
  • GitHub Desktop or Git CLI

No one needs VS Code unless they personally want it for a coding agent or editor. Designers and artists do not open Visual Studio day to day; Visual Studio is installed so Unreal has the C++ compiler toolchain available when the build script needs it.

Daily workflow

  1. Pull latest from Rephrased-Games/Rephrased-Game.
  2. Run [OpenAfterPull]Build_Project.bat.
  3. Work on a branch.
  4. Open a PR.
  5. Merge only after review/approval.

Use [OpenAfterPull]Build_Project.bat -check for setup diagnostics. Prefer -check, not /check, because Git Bash/MSYS can rewrite slash arguments.

Binary zip status

Rephrased_Binaries.zip is not the primary workflow. It may exist as an optional fallback/archive, but the official team setup is local toolchain build through [OpenAfterPull]Build_Project.bat.

PR discipline

Standard workflow is branch -> PR -> review/approval -> merge. No direct main pushes.

MCP create_branch starts standard task branches, and local Git hooks block commits/pushes on main/master, detached HEAD, and invalid branch names. GitHub branch protection is still planned once Education/private-repo benefits allow server-side enforcement.

MCP state

Rephrased MCP lives in the main game repo at tools/rephrased-mcp/.

Expected tools:

  • onboarding
  • create_branch
  • convention_check
  • request_review
  • wiki_query
  • devlog

MCP is useful, but it is not the first setup blocker. Repo access, UE 5.8, VS 2026, and the build script come first. MCP covers branch creation, onboarding, convention check, team review/request review, wiki search/query, and devlog. The review key and local config must never be committed.

Accretion/task tools are retired from the current Rephrased MCP.

First meeting priority

  1. Confirm GitHub org/repo access.
  2. Install UE 5.8 and VS 2026 with .vsconfig.
  3. Clone Rephrased-Games/Rephrased-Game.
  4. Run [OpenAfterPull]Build_Project.bat -check.
  5. Run the bat normally and open Rune Showcase.
  6. Set up Rephrased MCP after project launch works.

Standalone wiki/toolkit repos are not required for first setup.

Change history

  • 2026-08-27 - Gabriel Li - Added MCP create_branch and local hook branch guardrails; GitHub protection remains the server-side follow-up.
  • 2026-08-26 - Gabriel Li - Added Cloudflare live wiki deployment source note after org migration.
  • 2026-08-26 - Gabriel Li - Created after org migration, VS-once workflow decision, standalone repo bootstrap/sync, and first-meeting readiness work.