Create or update a pull request from the current branch using its actual commits and changes. Fill the repository template with a concrete description, reviewer test steps, and accurately reported checks, then push the branch.
Open or update a pull request on pascalorg/editor from the current branch, describing only what the branch actually did. Use when the user asks to open/create a PR, push and PR, or ship a branch in the editor repo.
Review the instructions the agent will receive before you install.
Open (or refresh) a pull request against pascalorg/editor from the current branch.
git branch --show-current # not main
git status --short # nothing uncommitted you weren't asked to commit
base=$(git merge-base HEAD origin/main)
git log --oneline --first-parent --no-merges "$base"..HEAD
git diff --stat "$base"..HEAD
The PR describes only these commits and this diff. Work that arrived by merging main, reverted commits, and patch-equivalent cherry-picks are not this PR's claims. If a file in the diff has no commit on the branch explaining it, stop and ask.
Run bun run check-types when the change is non-trivial; never claim a check you did not run.
.github/pull_request_template.md is the source of truth for headings and checklist. Fill it from §1, not from memory:
Fixes #123 when applicable.Not added yet. for a visual change without media, or N/A — non-visual change.bun dev only after a real local run).Title: under ~70 characters, a concrete result (not "update"/"improve"), scope-prefixed when one package owns it (core:, viewer:, editor:, nodes:, mcp:).
git push -u origin HEAD
gh pr view --json number,url,body 2>/dev/null # existing PR?
gh pr create --title … --body "$(cat <<'EOF' … EOF)".gh pr edit <n> --body …: rebuild "What" and "How to test" from the current branch, keep the media section and the reviewer's checklist ticks verbatim, keep any extra sections at the end. Change the title only if the scope changed.End the body with the attribution lines the session asks for, if any.
PR URL, title, which checks you ran, and anything left unchecked for the reviewer.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Check whether furniture occupies an available measured floor area in Pascal, including rotation, overlap, and required spacing. Receive a spatial report that separates verified floor fit from unverified height, door movement, and delivery conditions.
Create and edit rooms or buildings in Pascal through MCP, a connection that lets agents use its tools. Inspect existing projects, validate changes, and hand over saved, editable 3D scenes with verified editor links.
Review Pascal pull requests or branches against documented architecture rules. Check package responsibilities, node extension patterns, state management, and rendering subscriptions to identify misplaced code, compatibility breaks, and changes that could cause excessive redraws.