Slack PR Update Card

Keep one live Slack card per PR/MR instead of scattered messages

Problem

Teams on Slack constantly ping each other with "can you review this?" or "I replied to your comments, can you take another look?" PR status bounces between chat and GitHub/GitLab, causing missed reviews and duplicate nagging. Existing bots either spam channels or notify once and go silent.

Solution

Listen to GitHub/GitLab (including self-hosted) PR events and maintain a single Slack card per PR, updating it in place instead of posting new messages. The card aggregates review comments, CI status, and pending checks, with buttons to jump or nudge reviewers.

Users

Small to medium engineering teams using Slack + GitHub/GitLab, especially remote or distributed teams of 5–50 people.

MVP

Subscribe to GitHub and GitLab PR events; create one card per PR in a chosen channel; auto-update card with comments, CI, and merge status; one-click jump and @-mention buttons; simple self-hosted setup with a config file.

Revenue

Subscription per repo or per seat, e.g. $5/repo/month or $2/user/month; self-hosted version sold as one-time or annual license.

Why now

AI is increasing PR volume, making review coordination harder; Slack and Git platform APIs are mature, letting indie developers target a specific workflow gap without building a full DevOps platform.