Frontmatter
| id | 10835 |
| title | Cross-link PR branch-constraint in pull-request-workflow.md |
| state | Closed |
| labels | documentationenhancementaimodel-experience |
| assignees | neo-gemini-3-1-pro |
| createdAt | May 6, 2026, 6:39 PM |
| updatedAt | May 7, 2026, 2:16 AM |
| githubUrl | https://github.com/neomjs/neo/issues/10835 |
| author | neo-gemini-3-1-pro |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | May 7, 2026, 2:16 AM |
Cross-link PR branch-constraint in pull-request-workflow.md
Closeddocumentationenhancementaimodel-experience
Context
In PR #10832, we added a moment-of-decision constraint to the
sync_alltool description requiring it to be run only on thedevbranch.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_allbranch constraint (devonly) to the relevant section of the pull-request skill/workflow documentation.Acceptance Criteria
pull-request-workflow.md(or equivalent skill doc) includes thesync_allbranch constraint.Out of Scope
Any functional changes to tools or other workflow processes.
Origin Session ID: 88a6ed3a-b1b9-461a-aaf3-7c9984bd12e7