slack-approval-pr-automation

Automate Slack finding triage, human approval gating, and GitHub PR creation.

Updated May 15, 2026
One-click install
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill slack-approval-pr-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slack-approval-pr-automation
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/slack-approval-pr-automation
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill slack-approval-pr-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually routing Slack engineering findings to GitHub PRs, managing human approval gates, and tracking PR status is time-consuming and prone to human error for engineering teams.

Core Features & Use Cases

  • Lightweight Sentinel Watchers: Cheap, low-reasoning automations that scan Slack channels for actionable findings, deduplicate existing work, and only escalate real new issues to high-reasoning workers.
  • Approval-Gated Workflows: Uses $handle-in-slack to request explicit YES/NO approval from humans in Slack before any code changes, PR creation, or side effects are executed.
  • End-to-End PR Automation: Spawns deep triage workers to analyze findings, create PRs, and run PR-specific watchers that handle CI feedback, auto-fixes, and merging when approved.
  • Use Case: Engineering teams using Slack for incident reports, bug submissions, or code change requests can automate the full workflow from initial Slack message to merged PR without manual handoffs.

Quick Start

Use the slack-approval-pr-automation skill to set up a Slack watcher that automatically escalates approved engineering findings to GitHub PR creation and tracking.

Frequently Asked Questions about slack-approval-pr-automation

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

FAQPage Schema
How do I automate GitHub PR creation from Slack messages?

Automating GitHub PR creation from Slack messages requires a watcher to triage findings, route them through human approval gates, and spawn workers to create and track the PR end-to-end. This skill handles that full workflow using sentinel watchers and deep triage workers.

What is an approval-gated workflow for engineering Slack channels?

An approval-gated workflow for engineering Slack channels intercepts actionable findings, requests explicit YES/NO human approval in Slack, and blocks any code changes or PR creation until approval is granted. This prevents unauthorized side effects and ensures human oversight.

How do I deduplicate engineering findings in Slack to avoid duplicate PRs?

Deduplicating engineering findings in Slack requires lightweight sentinel watchers to scan channels, identify existing work, and only escalate genuinely new issues to high-reasoning triage workers for PR creation. This reduces manual overhead and prevents duplicate pull requests.

Can I use Slack automation to track GitHub PR status and CI feedback?

Slack automation can track GitHub PR status and CI feedback by spawning PR-specific watchers that monitor CI results, trigger auto-fixes, and manage merging after approval. This provides end-to-end tracking from the initial Slack message to the final merged PR.

What's the best way to manage incident reports in Slack without manual handoffs?

Managing incident reports in Slack without manual handoffs involves deploying sentinel watchers to detect actionable findings, routing them through approval gates, and automating PR creation and tracking. This eliminates manual routing errors and accelerates incident resolution.

Do I need human approval before this Slack automation executes code changes?

Human approval is required before this Slack automation executes code changes, creates PRs, or performs any side effects. The workflow uses explicit YES/NO approval gating in Slack to ensure no code modifications happen without human confirmation.