PRs merge themselves.

Autonomous rebasing, conflict resolution, build verification, slot sync, and learning extraction. Guardian handles the last mile so you don't have to.

Part of Traqr CLInpx @traqr/cli init
The merge lifecycle

Scan. Rebase. Merge. Learn.

01

Scan

Guardian monitors open PRs. Checks build status, conflict potential, dependency chains.

02

Rebase

Automatically rebases onto main. Detects and attempts conflict resolution before escalating.

03

Merge

Build verification, safety checks, merge execution. Never merges broken builds. Never force-pushes.

04

Learn

Post-merge: sync all worktree slots, extract learnings to TraqrDB, notify Slack, clean up branches.

guardian — merge lifecycle
Guardian scanning PR #1065...
✓ Rebased onto main (3 commits ahead)
✓ No conflicts detected
✓ Build passed (1.6s)
✓ Merged to main
Post-merge:
✓ 18 worktree slots synced
✓ 2 learnings extracted to TraqrDB
✓ Branch cleaned up
✓ Slack notified: #control-center
Done. 34 seconds total.

Autonomous, not reckless.

Guardian never force-pushes. Never merges broken builds. When it can't resolve a conflict, it escalates to Slack with full context — what conflicted, why, and suggested resolution steps.

Build gate

Every PR must pass a full build before Guardian will merge. No exceptions.

Smart escalation

Conflicts get analyzed, not ignored. Guardian posts to Slack with the exact files, functions, and suggested fix.

Learning loop

Every merge teaches TraqrDB something. Patterns, gotchas, and decisions compound across the entire team.