bug-bash SKILL.md skillA
bug-bash from beakpoint-insights/roost is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add beakpoint-insights/roost/bug-bash@git:20261026.505a1daPins git:20261026.505a1da in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- beakpoint-insights/roost
- Path
skills/bug-bash/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261026.505a1da, committed Oct 26, 2026
- First version recorded
- Oct 26, 2026
- Size
- 6,054 bytes
- Repository stars
- 30
- License
- MIT
Fix a list of bugs from the tracker in this repo, one branch each, test-first, with each fix placed by its parent (on the epic's GitHub stack for a bug in an unreleased epic, or its own PR from main for a standalone bug), moving each ticket through In Progress and Ready for Release. When a fix needs another repo, hand it off with pasteable comments instead of touching it. Use when the user gives a list of bugs to fix, says "bug bash", or pastes a "Big Bug Fix Bash" prompt.
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
# Bug Bash Fix several bugs in one session, each on its own branch, and keep the tracker in step. Each fix goes where its bug belongs: on its epic's stack, or on its own PR from `main` (see "Where the branch goes"). **First, load the team config with `roost-config`.** ## Inputs Ask for anything missing, in one message: - **The bugs:** ticket keys. - **This repo:** which of the config's `repos` this session is in (its working directory usually says). Every other repo is off-limits. - **Where each fix goes** comes from the bug itself (see "Where the branch goes" below). Ask only if the user named a stack that contradicts it. - Anything the user wants different from the defaults below. ## Where the branch goes Read the bug's parent in the tracker: | Bug | Branch | PR | Release | |---|---|---|---| | **Part of an epic that isn't released yet** (see below) | On top of the epic's stack in this repo: the highest branch of that epic, found with `gh stack` or the epic's **Release order** comment | On the epic's stack, with the "Stacked on" banner; add it to the epic's Release order comment | Ships with the epic | …
Read the whole file at its exact version.
How to install
mdr add beakpoint-insights/roost/bug-bash@sha256:4bbd7a760e32a574The line at the top of this page pins the label git:20261026.505a1da, 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_k7f6sdqtvb2gu3xe)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Oct 26, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.505a1da latest | 2026-10-26 | 505a1da | 6,054 B | A | view · diff |
| git:20261026.66cdcd9 | 2026-10-26 | 66cdcd9 | 6,068 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 (6054 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
beakpoint-insights/roost · 30 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_k7f6sdqtvb2gu3xe GET https://markdownregistry.com/api/v1/resolve?ref=beakpoint-insights/roost/bug-bash GET https://markdownregistry.com/api/v1/blob/4bbd7a760e32a5747a850925f9039ceba2af288ce437cbf828b22059aa3e041c
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.
More from beakpoint-insights/roost
Every file in beakpoint-insights/roost