ship

Notify a Slack channel to request PR reviews after CI checks pass.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/julianjab/ia-tools --skill ship-julianjab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/julianjab/ia-tools/tree/main/skills/ship
Command: npx skills add https://github.com/julianjab/ia-tools --skill ship-julianjab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow coordinates PR reviews by notifying a Slack channel once CI checks have passed, ensuring timely feedback on changes.

Core Features & Use Cases

  • Waits for all CI checks to pass on an existing PR, then prompts for review in a Slack channel.
  • Supports overriding the target channel and mentions via arguments, or falls back to CLAUDE.md ship config.
  • Finds or creates a Slack thread for the PR review and subscribes to the thread after posting.

Quick Start

Run /ship to initiate the PR review notification workflow after CI passes.

Frequently Asked Questions about ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Slack notifications for GitHub PR reviews after CI passes?

You can automate PR review notifications by running the /ship command to wait for CI checks to pass, then automatically post or reply in a Slack thread to request reviews. It resolves target channels and mentions from arguments or CLAUDE.md config.

Can I override the target Slack channel and mentions for PR review requests?

Yes, you can override the target Slack channel and mentions via command arguments. If no arguments are provided, the workflow falls back to reading default configurations from the CLAUDE.md ship config file.

How do I find and manage Slack threads for existing GitHub PR review requests?

The workflow queries existing Slack threads to find a matching conversation for your PR. If no thread exists, it creates a new one, posts the review request, and subscribes to the thread to track subsequent replies.

Does this PR review notification workflow work without a pre-existing GitHub PR?

No, this workflow applies to GitHub PR workflows where a pull request is already created. It specifically waits for the CI status on that existing PR to pass before prompting reviewers in Slack.

Do I need to manually trigger the Slack notification when CI checks pass?

No, you do not need to manually trigger the Slack notification. After you run /ship, the workflow waits for all CI checks to pass on the PR and then automatically prompts the configured reviewers.

What is the best way to coordinate team communication for PR reviews across GitHub and Slack?

The best way to coordinate PR reviews is using an automated workflow that bridges GitHub and Slack by waiting for CI checks to pass, then finding or creating a dedicated Slack thread to request and track team feedback.