Detects the current owner
Classifies work as waiting for automated checks, human review, author fixes, merge, or completion.
Repository review operations
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.
Capabilities
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.
Classifies work as waiting for automated checks, human review, author fixes, merge, or completion.
Uses repo-level handoff, escalation, infra, and test-channel settings with per-repo mute controls.
Checks repo ownership, missing connections, chat readiness, status mapping, and notification paths.
Reviewer, author, and merger SLA windows can trigger reminders before ownership gets lost.
Business-hours and daily digest settings keep open review obligations visible in the team timezone.
Tenant data, secrets, configs, install links, runtime state, and audit events are isolated by workspace.
Workflow
A PR/MR opens or changes state, then Sentinel applies the repository defaults and ownership rules.
Status checks, review bots, security scans, or CI signals can block or release the review path.
Reviews, comments, requested changes, approvals, and merge readiness update the current owner.
Chat alerts and project-management stages stay in sync until the work is merged or closed.
Integrations
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.
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.
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.
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.
GitHub check gates support SonarQube, SonarCloud, CodeRabbit, Codacy, CodeQL, Greptile-style checks, or any tool that reports predictable check names.
AWS API Gateway, Lambda, DynamoDB, Secrets Manager, EventBridge Scheduler, CloudWatch, WAF, and least-privilege IAM back the production deployment.
Additional source-control, chat, and project-management tools need adapter implementation and provider credentials before they are available inside a tenant workspace.
Controlled access
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.
Request access
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
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.