Repository review operations

Keep every review moving from open to merged.

PR Sentinel coordinates repository review events, quality gates, team chat handoffs, and project-status stages so authors, reviewers, and release owners always know who owns the next step.

Repo-levelEach repository owns its routing and rules
Live adaptersGitHub, Slack, Linear, quality checks
ServerlessAWS Lambda, API Gateway, DynamoDB

Capabilities

What the platform does

PR Sentinel is an operations layer for pull requests and merge requests. It does not replace your source-control, review, chat, or project-management tools; it connects them around a single owner-state model for every repository.

Review state

Detects the current owner

Classifies work as waiting for automated checks, human review, author fixes, merge, or completion.

Routing

Notifies the right channel

Uses repo-level handoff, escalation, infra, and test-channel settings with per-repo mute controls.

Guardrails

Validates onboarding before launch

Checks repo ownership, missing connections, chat readiness, status mapping, and notification paths.

Escalation

Keeps stale work visible

Reviewer, author, and merger SLA windows can trigger reminders before ownership gets lost.

Digest

Summarizes unresolved work

Business-hours and daily digest settings keep open review obligations visible in the team timezone.

Multi-tenant

Separates customer workspaces

Tenant data, secrets, configs, install links, runtime state, and audit events are isolated by workspace.

Workflow

How repository work moves through Sentinel

1

Repo event arrives

A PR/MR opens or changes state, then Sentinel applies the repository defaults and ownership rules.

2

Quality gates report

Status checks, review bots, security scans, or CI signals can block or release the review path.

3

Owner is assigned

Reviews, comments, requested changes, approvals, and merge readiness update the current owner.

4

Teams stay aligned

Chat alerts and project-management stages stay in sync until the work is merged or closed.

Integrations

Tool-agnostic by design, explicit about what is live

The current deployment has working adapters for GitHub, Slack, Linear, GitHub checks, and AWS serverless hosting. The product model is repo-level, so GitLab, Bitbucket, Jira, Asana, Azure Boards, Teams, and similar systems fit as additional adapters.

Git providers Live now

GitHub App install links, webhooks, PR state tracking, review reconciliation, and draft/ready sync are implemented. GitLab or Bitbucket can use the same repository-event contract as the next provider adapters.

Team chat Live now

Slack OAuth, signed events, handoff messages, escalations, infra alerts, dry-run test sends, and channel-level controls are implemented. Teams or Google Chat can follow the same notification adapter shape.

Project tools Live now

Linear status mapping is implemented for pending review, in review, changes requested, ready to merge, and done. Jira, Asana, Azure Boards, or ClickUp would map to the same stage model.

Review gates Live now

GitHub check gates support SonarQube, SonarCloud, CodeRabbit, Codacy, CodeQL, Greptile-style checks, or any tool that reports predictable check names.

Cloud runtime Live now

AWS API Gateway, Lambda, DynamoDB, Secrets Manager, EventBridge Scheduler, CloudWatch, WAF, and least-privilege IAM back the production deployment.

Future adapters Planned gap

Additional source-control, chat, and project-management tools need adapter implementation and provider credentials before they are available inside a tenant workspace.

Controlled access

Owner-approved workspaces

Production signup is intentionally gated. New teams request access, the platform owner creates or approves the workspace, then the tenant owner receives credentials and connects repo, chat, project-management, and review-gate integrations.

Platform owner: create, suspend, reactivate, impersonate, audit, and manage tenant workspaces.
Tenant owner: connect integrations, add repositories, validate guardrails, test notifications, and tune advanced config.
Repo-level control: configure channels, reviewers, merge ownership, SLA windows, digests, quality gates, and project stages per repository.
Security: CSRF protection, rate limits, secure cookies, signed install links, encrypted tenant secrets, WAF, and least-privilege IAM.

Request access

Ask for a workspace

Send the details needed to create your workspace and grant access. The request is stored in the owner audit queue so the platform owner can review it, create the tenant, and confirm the right integration path.

Include the tools you use today and any provider gaps you need covered. If the tool is not available yet, it becomes an explicit adapter requirement instead of a hidden promise.

Deployment state

Ready for controlled rollout

PR Sentinel is live as a secure AWS serverless deployment with gated tenant access. Request a workspace first, then use the app login once access has been granted.