What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	10428
title	Implement reviewer-side audit for PR keyword syntax in pr-review-guide.md
state	Closed
labels	documentationenhancementaiarchitecture
assignees	[]
createdAt	Apr 27, 2026, 3:42 PM
updatedAt	Apr 27, 2026, 5:53 PM
githubUrl	https://github.com/neomjs/neo/issues/10428
author	neo-gemini-pro
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 27, 2026, 5:53 PM

Implement reviewer-side audit for PR keyword syntax in pr-review-guide.md

Closed v13.0.0/archive-v13-0-0-chunk-6 documentationenhancementaiarchitecture

neo-gemini-pro commented on Apr 27, 2026, 3:42 PM

Context During the review of PR #10427, it was identified that while the author-side mandate for exact PR closing syntax (e.g., Resolves #N on a separate line) is codified in pull-request-workflow.md, the corresponding reviewer-side check is missing.

The Problem pr-review-guide.md §5.2 Ticket Resolution Audit currently audits validity (epic vs leaf issue closures) but lacks an explicit audit for syntax correctness (newline-isolated vs prose-embedded or comma-separated). This creates an asymmetry where authors are instructed on strict syntax, but reviewers are not prompted to enforce it.

The Architectural Reality .agent/skills/pr-review/references/pr-review-guide.md §5.2 Ticket Resolution Audit is the canonical reviewer-side checklist for verifying PR closures.

The Fix Add an explicit audit step in pr-review-guide.md §5.2 requiring reviewers to verify that PR bodies adhere to the "Syntax-Exact Keyword Mandate." Reviewers must ensure that closing keywords (like Resolves #N) are isolated on their own lines and that multiple tickets are closed on separate lines, rejecting prose-embedded or comma-separated closures.

Acceptance Criteria

Update .agent/skills/pr-review/references/pr-review-guide.md §5.2 to include the Syntax-Exact Keyword Mandate audit.
Explicitly instruct reviewers to request changes if a PR uses embedded or comma-separated closing keywords.

Out of Scope

Implementing GitHub Actions or automated API checks for this syntax. Enforcement remains procedural via the agent skill docs.

Related

Sibling to the author-side update from PR #10427.

Origin Session ID: 49e9b05a-0581-4fb7-861f-7e4970ea4c2b

tobiu referenced in commit f198285 - "feat/fix(ai): Support @me addressing in MailboxService and mandate exact PR close syntax (#10426) (#10427) on Apr 27, 2026, 5:53 PM

tobiu closed this issue on Apr 27, 2026, 5:53 PM