bd-issue-push skillA
bd-issue-push is agent-read markdown (skill) from petar-djukic/coding-skills: Create a bead (task) in the current repository using beads (`bd`). Beads keeps its database in the main repo checkout and its tracked `issues.jsonl` o.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# bd-issue-push command Apply this command workflow. Treat any text after its invocation as the command input. Create a bead (task) in the current repository using beads (`bd`). Beads keeps its database in the main repo checkout and its tracked `issues.jsonl` on `main`; `bd sync` persists new beads to git so they are visible on all machines. Run this from the main checkout on `main` (not inside a worktree). ## Input $ARGUMENTS ## Steps 1. Verify that `.beads/` exists in the repository root. If not, initialize beads and persist it: ```bash bd init bd sync # commits and pushes the tracked .beads/ files ``` 2. **Search for ripple effects.** Before drafting the bead, identify every file and field that the change touches — not just the primary target. The executor will do exactly what the bead says and nothing else, so anything omitted will be missed. - Read the files involved to understand their structure. - `grep` for identifiers, names, or values being added, changed, renamed, or deleted. Search the full project, not just the obvious files. - For each hit, note the file path, the field or line, and what needs to change. …
Read the whole file at its exact version.
How to install
mdr add petar-djukic/coding-skills/bd-issue-push@git:20260725.d478789mdr add petar-djukic/coding-skills/bd-issue-push@sha256:6227e372b554977ePin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ml63ffrqttmqydz5)
1 badge views in 30 days
Versions
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 (2198 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/coding-skills · 3 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ml63ffrqttmqydz5 GET https://markdownregistry.com/api/v1/resolve?ref=petar-djukic/coding-skills/bd-issue-push GET https://markdownregistry.com/api/v1/blob/6227e372b554977ea4756253fe54ec3056c76819bdd6e6457bb73391d5e272e3
Your agent 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.