Check Pr Conflicts · lazarus-ai bundle Detect direct Git merge conflicts, overlapping edits, semantic integration risks, and architectural convergence opportunities between the current branch or pull request and open GitHub pull requests, named active branches, or existing local/remote refs. Use before creating or submitting a PR, marking a PR ready, declaring a branch ready for review, during every PR/code-review readiness check, after significant rebases or base-branch updates, or when asked whether parallel engineering work may conflict or share a common architecture. Pair this check with normal code review and tests; it does not replace either.
