tech-log-test-failure-watcher

Monitor Slack #tech-log for api.pearcommerce.com test failures and triage them.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually monitoring the Pear #tech-log Slack channel for api.pearcommerce.com test failures, triaging root causes, creating fix PRs, and tracking merges is time-consuming and prone to missed alerts, especially during off-hours or high failure volumes.

Core Features & Use Cases

  • Lightweight Sentinel Monitoring: Runs a low-cost recurring check of #tech-log for new test failure notifications, with an off-hours quiet window to avoid unnecessary alerts.
  • Deep Automated Triage: Escalates unhandled failures to dedicated workers that analyze GitHub Actions logs, identify the most likely culprit merged PR, and tag the responsible author in Slack.
  • End-to-End Fix Workflow: Manages human approval gates, creates minimal fix PRs, watches for review feedback and CI checks, auto-merges when ready, and posts status updates to Slack.
  • Use Case: When a master branch integration test fails in #tech-log, the skill automatically detects the failure, identifies the breaking PR, gets team approval, opens a fix PR, and merges it once all checks pass without requiring manual tracking.

Quick Start

Use the tech-log-test-failure-watcher skill to start or repair the automated Slack #tech-log test failure monitoring and end-to-end triage workflow.

Frequently Asked Questions about tech-log-test-failure-watcher

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

FAQPage Schema
How do I automate CI test failure triage from Slack notifications?

Automate CI test failure triage by monitoring Slack channels for failure alerts, analyzing GitHub Actions logs to identify culprit PRs, tagging authors, and creating automated fix PRs. This eliminates manual tracking and resolves master branch test failures with minimal human intervention.

Can I automatically identify which PR caused a GitHub Actions test failure?

Yes, automated triage workers analyze GitHub Actions logs to identify the most likely culprit merged PR responsible for a test failure. The system then tags the responsible PR author in Slack for immediate awareness and follow-up.

What is the workflow for automating test failure fixes with human approval?

The workflow detects failures, analyzes CI logs, identifies the breaking PR, requests human approval via Slack, creates a minimal fix PR, monitors CI checks, and auto-merges when ready. This ensures test failures are resolved safely with gated human oversight.

Does CI failure monitoring work during off-hours without creating unnecessary alerts?

Lightweight sentinel monitoring runs low-cost recurring checks of Slack channels for test failure notifications and includes an off-hours quiet window. This prevents unnecessary alerts during nights or weekends while still catching critical master branch failures.

How to handle unhandled CI test failures that escalate beyond initial monitoring?

Unhandled failures escalate from sentinel monitoring to dedicated deep triage workers. These workers analyze GitHub Actions logs, identify the culprit merged PR, tag the responsible author in Slack, and manage the end-to-end fix workflow including PR creation and merging.