Skip to main content

SWE Merged PR Monitoring

Skill Verified Active
Part of:Swe Skills

Reviews recently merged pull requests, confirms whether they reached production, compares pre- and post-deploy signals, and summarizes observable impact. Use when a user says `monitor merged PRs`, `did this deploy hurt prod`, `check production impact of yesterday's merges`, or asks for a post-deploy readout tied to merged GitHub PRs. Do NOT use for a pre-merge code review, incident analysis with no PR scope, or generic dashboard triage disconnected from merged changes.

Purpose

To provide clear, data-driven insights into the production impact of merged code changes, connecting engineering effort directly to observable outcomes.

Features

  • Reviews merged pull requests
  • Confirms production deployment status
  • Compares pre- and post-deploy signals
  • Summarizes observable production impact
  • Supports various observability sources

Use Cases

  • Reviewing the production impact of recent merged PRs
  • Checking if a change reached production and moved metrics
  • Comparing pre- and post-deploy behavior for a set of merges
  • Producing concise engineering readouts tied to merged GitHub work

Non-Goals

  • Pre-merge code review
  • Root-cause analysis with no scoped PR set
  • Generic service monitoring not tied to merged changes
  • Product analytics reporting unrelated to deploys

Workflow

  1. Define Scope Precisely (repositories, author filters, timeframe)
  2. Collect The Merged PR Set (number, title, link, merge time)
  3. Map Likely Affected Surfaces (services, endpoints, jobs)
  4. Confirm Production Deployment (using deploy logs, release dashboards, etc.)
  5. Compare The Before And After Window (pre- and post-deploy metrics)
  6. Correlate Cautiously (connect metric changes to PRs only when evidence supports it)
  7. Write A Short PR-By-PR Report (concise, signal-focused, one section per PR)

Prerequisites

  • Access to GitHub PR metadata
  • Access to deployment and observability sources (CI/CD logs, metrics, traces, service health tools)

Installation

/plugin install swe-skills@ckorhonen-swe-skills

Quality Score

Verified
98 /100
Analyzed about 21 hours ago

Trust Signals

Last commit5 days ago
Stars1
LicenseMIT
Status
View Source

Similar Extensions

Ops Fires

100

Production incidents dashboard. Reads ECS health, Sentry errors, CI failures. Offers to dispatch fix agents for active fires.

Skill
Lifecycle-Innovations-Limited

ClawSweeper Skill

100

Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, commit-review reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions monitoring, permissions, gates, and manual backfills.

Skill
steipete

OPS ► CROSS PLATFORM TRIAGE

100

Cross-platform issue triage. Pulls from Sentry (MCP), Linear (MCP), GitHub Issues (gh). Cross-references against code to find already-fixed issues. Auto-resolves fixed ones. Dispatches agents for active issues.

Skill
Lifecycle-Innovations-Limited

Ci Cd Pipeline Builder

100

CI/CD Pipeline Builder

Skill
alirezarezvani

Setup Container Registry

99

Configure container image registries including GitHub Container Registry (ghcr.io), Docker Hub, and Harbor with automated image scanning, tagging strategies, retention policies, and CI/CD integration for secure image distribution. Use when setting up a private container registry, migrating from Docker Hub to self-hosted registries, implementing vulnerability scanning in CI/CD pipelines, managing multi-architecture images, enforcing image signing, or configuring automatic cleanup and retention policies.

Skill
pjt222

Github Project Management

99

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

Skill
ruvnet

© 2025 SkillRepo · Find the right skill, skip the noise.