swe:merged-pr-monitoring SKILL.md skillA
swe:merged-pr-monitoring from ckorhonen/swe-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ckorhonen/swe-skills/swe:merged-pr-monitoring@git:20260404.50aa7e9Pins git:20260404.50aa7e9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ckorhonen/swe-skills
- Path
skills/merged-pr-monitoring/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260404.50aa7e9, committed Apr 4, 2026
- First version recorded
- Apr 4, 2026
- Size
- 7,166 bytes
- Repository stars
- 3
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# SWE Merged PR Monitoring ## What This Skill Does Use this skill to connect merged code changes to production evidence without guessing. The expected output is a short, PR-by-PR report that answers: - What merged - Whether it deployed - What likely changed in production - What the observable impact was, if any ## When To Use Use this skill when the user wants to: - Review the production impact of recent merged PRs - Check whether a change reached production and moved metrics - Compare pre- and post-deploy behavior for a scoped set of merges - Produce a concise engineering readout tied to merged GitHub work ## Do Not Use Do not use this skill for: - 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 ## Inputs To Confirm Confirm or infer: - Repository or service scope - Author filter, if any - Time window - Production environment or environments to check - Available deployment and observability sources If the request leaves scope ambiguous, ask for the repo set, author filter, and time window before proceeding. ## Tooling Stance …
Read the whole file at its exact version.
How to install
mdr add ckorhonen/swe-skills/swe:merged-pr-monitoring@sha256:9b985adad757f822The line at the top of this page pins the label git:20260404.50aa7e9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_pcklfvrolmrktysz)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Apr 4, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260404.50aa7e9 latest | 2026-04-04 | 50aa7e9 | 7,166 B | A | view · diff |
| git:20260404.f3a9e33 | 2026-04-04 | f3a9e33 | 5,062 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7166 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ckorhonen/swe-skills · 3 stars · license MIT · pushed 2026-09-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pcklfvrolmrktysz GET https://markdownregistry.com/api/v1/resolve?ref=ckorhonen/swe-skills/swe:merged-pr-monitoring GET https://markdownregistry.com/api/v1/blob/9b985adad757f82282604027977a489971c55d90534248af4b4be1915dc30feb
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.