bd-issue-pop SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
bd-issue-pop from petar-djukic/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add petar-djukic/agent-skills/bd-issue-pop@git:20261013.4e1baf7Pins git:20261013.4e1baf7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- petar-djukic/agent-skills
- Path
.agents/skills/bd-issue-pop/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261013.4e1baf7, committed Oct 13, 2026
- First version recorded
- Jul 26, 2026
- Size
- 8,936 bytes
- Repository stars
- 3
- License
- MIT
Pop a bead (epic) into a worktree branch, decompose it into child beads, then.
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
# bd-issue-pop command Apply this command workflow. Treat any text after its invocation as the command input. Pop a bead (epic) into a worktree branch, decompose it into child beads, then hand off to `/do-work`. Mirrors the gh flow: this command sets up, `/do-work` does the work, and its last pass merges the PR and closes the epic. Two stores, and keeping them separate matters. The epic's **code** lands on the one `bd-<id>-<slug>` branch and merges via its single PR. The **bead tracker** lives in the shared main-repo database — worktrees reach it through a `.beads/redirect` — and persists with `bd sync`. Bead status never rides the code branch. ## Input $ARGUMENTS A bead ID. Without one, run `bd list` and ask which. ## Phase 0-2 -- Sync, fetch, gather context ```bash gh repo view --json nameWithOwner -q .nameWithOwner # <owner>/<repo>, for Phase 5 git pull && bd sync git branch --show-current # must be main, not a worktree bd show <id> ``` Stop if you are not on `main` in the main checkout, or if the bead is already done. Show the bead's title and description. Read `docs/VISION.yaml`, `docs/ARCHITECTURE.yaml`, `docs/road-map.yaml`, …
Read the whole file at its exact version.
How to install
mdr add petar-djukic/agent-skills/bd-issue-pop@sha256:d04ecc23147ad0a2The line at the top of this page pins the label git:20261013.4e1baf7, 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_3wf3msc7l7jh6m4g)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 26, 2026 and Oct 13, 2026, about one every 20 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261013.4e1baf7 latest | 2026-10-13 | 4e1baf7 | 8,936 B | A | view · diff |
| git:20260920.1216b82 | 2026-09-20 | 1216b82 | 8,663 B | A | view · diff |
| git:20260920.545799f | 2026-09-20 | 545799f | 8,646 B | A | view · diff |
| git:20260813.79bf4fd | 2026-08-13 | 79bf4fd | 7,995 B | A | view · diff |
| git:20260726.8e7c950 | 2026-07-26 | 8e7c950 | 7,341 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 (8936 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
petar-djukic/agent-skills · 3 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3wf3msc7l7jh6m4g GET https://markdownregistry.com/api/v1/resolve?ref=petar-djukic/agent-skills/bd-issue-pop GET https://markdownregistry.com/api/v1/blob/d04ecc23147ad0a2524136fa626a29131926ad39b31b8c8737a20676841757c8
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 petar-djukic/agent-skills
Every file in petar-djukic/agent-skills