gitnexus-pr-review

The gitnexus-pr-review skill provides automated, graph-powered intelligence for reviewing pull requests. Designed for software engineers and development teams, it moves beyond simple code diffing by utilizing the GitNexus knowledge graph to understand how specific changes propagate through your architecture. It is ideal for identifying high-risk changes, verifying test coverage, and ensuring that refactoring or feature additions do not inadvertently break upstream callers or downstream dependencies. By mapping changes to execution flows—such as payment processing, checkout flows, or authentication handlers—the agent can provide a comprehensive risk assessment, ranging from low to critical. It detects missing test coverage and alerts reviewers to potential breaking changes that might otherwise be overlooked in manual reviews.

• Perform deep structural analysis on PR diffs to map changes to affected code symbols and execution flows.

• Assess the 'blast radius' of changes, showing d=1, d=2, and d=3 dependents to prevent regression errors.

• Automatically check for upstream callers that are not updated within the PR, flagging potential breakage.

• Verify test coverage by correlating changed symbols with relevant unit and integration tests.

• Utilize gitnexus_detect_changes, gitnexus_impact, and gitnexus_context tools to build a visual and data-driven summary of PR health.

• Generate structured review reports including risk levels, findings, and actionable recommendations.

• Ensure compatibility with standard Git workflows and existing CI/CD pipelines.

• Always run 'npx gitnexus analyze' before reviewing to ensure the knowledge graph index is up-to-date.

• Best suited for complex repositories where manual dependency tracking is error-prone.

• The output includes clear severity indicators, evidence-based findings, and explicit instructions for approval or requested changes.

• Effectively bridges the gap between raw diffs and architectural impact, providing confidence for faster merge cycles.

• Input requirements include a valid PR number; the agent fetches the diff and parses symbols using the underlying GitNexus architecture.

• Note: Requires the GitNexus CLI and indexer to be pre-configured in your project repository.