Skip to content

MOB-51822: Add Slack ready-for-review notification to prisma-taurus skill#2004

Merged
mykhaliev1 merged 1 commit into
masterfrom
slack-ready-for-review-prisma-taurus
Jul 10, 2026
Merged

MOB-51822: Add Slack ready-for-review notification to prisma-taurus skill#2004
mykhaliev1 merged 1 commit into
masterfrom
slack-ready-for-review-prisma-taurus

Conversation

@RafaelGuevaraCA

Copy link
Copy Markdown
Collaborator

Jira: MOB-51822

Skill-documentation change to .claude/skills/prisma-taurus/SKILL.md. No product code, Dockerfile, or requirements changes — only the SKILL.md file. Mirrors the sibling change made to the taurus-cloud CVE skills (MOB-51821, Blazemeter/taurus-cloud#789).

What this adds

A new step 17 that posts a single Slack chat.postMessage "ready for review" summary once the PR exists and Copilot's one triage round is done (or timed out) — signalling the PR is basically ready for human review.

  • Best-effort — never fails, blocks, or errors the run (same discipline as the optional GitHub Copilot reviewer request). Missing vars, curl/network/timeout/JSON errors, and Slack ok:false are all caught.
  • Registers two optional env vars SLACK_BOT_TOKEN / SLACK_SPARTA_CHANNEL_ID; skips cleanly if either is unset. The three required creds still hard-stop.
  • Only posts when a PR was created. Content is only the fixed CVEs (Y), grouped by package with CVEs listed vertically; the count is computed from the fixed list.
  • Locked, shared format (bot "Sparta Scan"): 🛠️ Prisma CVE fixes ready for review — taurus #<PR> · N CVEs fixed · <MOB-XXXXX>. Byte-identical to the taurus-cloud version except the repo/link wording (taurus #<PR>) and the Prisma scan-type tag.
  • Escapes Slack mrkdwn metacharacters (& < >) in dynamic text so version constraints (e.g. <13.0.0) render literally; drops the Jira segment entirely when no ticket exists (headless/cron).

Placement

Inserted after the Copilot-triage step (step 16). Fires on every exit path, including the Copilot-timeout path (step 16a's "go to step 17" now lands on it). Trailing steps renumbered (Report 17→18, Final summary 18→19) and a Slack: outcome line added to the final summary.

Verification

  • Self-reviewed via superpowers:requesting-code-review — no Critical/Important findings; step numbering integrity and best-effort error handling confirmed.
  • Payload-build logic dry-run validated (escaping + no-Jira omission + computed count + json.dumps round-trip).
  • The exact snippet was exercised against real PR data (MOB-51648: CVE fixes - 2026-07-07 #2002), posting to a DM (not the channel) to confirm the rendered format.

🤖 Generated with Claude Code

…rus skill

Mirrors Blazemeter/taurus-cloud#789. Adds a best-effort final Slack
chat.postMessage summary (new step 17) after Copilot triage, registers
optional SLACK_BOT_TOKEN / SLACK_SPARTA_CHANNEL_ID env vars, and renumbers
the trailing steps (Report 17->18, Final summary 18->19). The post is
best-effort: it never fails, blocks, or errors the run, skips cleanly if
unconfigured, and only fires when a PR was created. Doc-only change.

Jira: MOB-51822

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@mykhaliev1 mykhaliev1 merged commit 7257724 into master Jul 10, 2026
1 check passed
@mykhaliev1 mykhaliev1 deleted the slack-ready-for-review-prisma-taurus branch July 10, 2026 10:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants