Skip to main content

​
The Problem

AI coding assistants accelerate code production — not code quality. Teams ship faster and accumulate defects faster. Code reviews become rubber stamps. Standards drift.

​
What It Does

A 5-point pre-merge gate that blocks the merge — not advisory:
  1. Acceptance criteria compliance
  2. AI anti-pattern detection
  3. Test smell analysis
  4. Security vulnerability scan
  5. External dependency audit

​
Try It

activate nablr
Set agent to pr_reviewer. Review the changes in this PR
With a specific file or PR in focus: 
Set agent to pr_reviewer. Review changes in src/auth.py for compliance and AI anti-patterns
For the full parallel gate: 
Set agent to pr_reviewer. Run full pre-merge gate
Set agent to tester. Run test smell analysis
Set agent to security_owner. Run security audit

​
Expected Output

  • Pass/fail merge verdict
  • Per-violation report with file + line references
  • Blocked merge with required fixes listed

​
Who This Is For

  • Teams using Cursor, Copilot, or Claude for development who cannot trust what ships
  • Engineering leads responsible for production stability
  • DevOps and platform teams setting quality floors
ShipSafe is a blocking gate, not a linter. A failing check means no merge until resolved or explicitly deferred with documented rationale.