swe:recent-commit-bug-hunt SKILL.md skillA
swe:recent-commit-bug-hunt 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:recent-commit-bug-hunt@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/recent-commit-bug-hunt/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260404.50aa7e9, committed Apr 4, 2026
- First version recorded
- Apr 4, 2026
- Size
- 7,047 bytes
- Repository stars
- 3
- License
- MIT
Scans recent commits in one or more repositories, identifies likely bugs using concrete repo evidence only, and proposes tightly scoped remediation sessions. Use when a user says `scan recent commits for bugs`, `what did I probably break`, `review yesterday's changes for regressions`, or asks for a commit-scoped bug hunt. Do NOT use for a broad code health review, full security audit, or speculative bug hunting with no repo or time scope.
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 Recent Commit Bug Hunt ## What This Skill Does Use this skill to inspect recent code changes conservatively and separate: - Real regression signals - Plausible but weaker suspicions - Noise that should not become a fix proposal The outcome should be a ranked list of evidence-backed findings plus small, behavior-focused remediation sessions for the findings that clear the bar. ## When To Use Use this skill when the user wants to: - Review recent commits for likely regressions - Check whether their latest changes introduced bugs - Mine recent PRs or SHAs for concrete bug signals - Propose narrowly scoped follow-up fix sessions ## Do Not Use Do not use this skill for: - A generic code smell review - A security or dependency audit - A large-scale refactor plan - Speculative bug hunting with no commit scope ## Inputs To Confirm Confirm or infer: - Repository set - Author filter, if any - Time window - Whether linked PR or CI context is available - Whether local validation can be run If scope is missing, ask for the repo set, author, and timeframe before proceeding. ## Evidence Sources Concrete evidence includes: - Commit SHAs - Pull requests - File paths - Diffs …
Read the whole file at its exact version.
How to install
mdr add ckorhonen/swe-skills/swe:recent-commit-bug-hunt@sha256:d8cc3eb9462d3765The 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_i2apqahke7uf6shv)
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,047 B | A | view · diff |
| git:20260404.f3a9e33 | 2026-04-04 | f3a9e33 | 4,506 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 (7047 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_i2apqahke7uf6shv GET https://markdownregistry.com/api/v1/resolve?ref=ckorhonen/swe-skills/swe:recent-commit-bug-hunt GET https://markdownregistry.com/api/v1/blob/d8cc3eb9462d3765c55bfaadd9d5c3cf95ff13801e0384a28f8b31cc9d8f6301
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.