LearnNewsExamplesServices
Frontmatter
id10835
titleCross-link PR branch-constraint in pull-request-workflow.md
stateClosed
labels
documentationenhancementaimodel-experience
assigneesneo-gemini-3-1-pro
createdAtMay 6, 2026, 6:39 PM
updatedAtMay 7, 2026, 2:16 AM
githubUrlhttps://github.com/neomjs/neo/issues/10835
authorneo-gemini-3-1-pro
commentsCount1
parentIssuenull
subIssues[]
subIssuesCompleted0
subIssuesTotal0
blockedBy[]
blocking[]
closedAtMay 7, 2026, 2:16 AM

Cross-link PR branch-constraint in pull-request-workflow.md

Closeddocumentationenhancementaimodel-experience
neo-gemini-3-1-pro
neo-gemini-3-1-pro commented on May 6, 2026, 6:39 PM

Context

In PR #10832, we added a moment-of-decision constraint to the sync_all tool description requiring it to be run only on the dev branch.

The Problem

To ensure symmetric authoring and tool-use discipline, this constraint should also be documented in our standard PR workflow guidelines.

The Architectural Reality

pull-request-workflow.md (or .agents/skills/pull-request/SKILL.md) dictates how agents handle branches and PRs.

The Fix

Add a cross-link or explicit mention of the sync_all branch constraint (dev only) to the relevant section of the pull-request skill/workflow documentation.

Acceptance Criteria

  • pull-request-workflow.md (or equivalent skill doc) includes the sync_all branch constraint.

Out of Scope

Any functional changes to tools or other workflow processes.

Origin Session ID: 88a6ed3a-b1b9-461a-aaf3-7c9984bd12e7

tobiu closed this issue on May 7, 2026, 2:16 AM
tobiu referenced in commit 8627739 - "docs(pull-request): map vs world atlas constraints (#10835) (#10853) on May 7, 2026, 2:16 AM