ship-change SKILL.md skillA
ship-change from blackbelttechnology/pi-agent-dashboard is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add blackbelttechnology/pi-agent-dashboard/ship-change@v1.1Pins v1.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- blackbelttechnology/pi-agent-dashboard
- Path
.pi/skills/ship-change/SKILL.md- Versions recorded
- 6
- Latest version
- v1.1, committed Oct 15, 2026
- First version recorded
- Jul 13, 2026
- Size
- 15,980 bytes
- Repository stars
- 341
- License
- MIT
Ship an OpenSpec change after openspec-apply completes. When only QA/manual tasks remain, marks them done (tested later), archives + syncs specs, commits, pushes, opens a PR against develop, watches CI, waits for CodeRabbit, auto-applies safe fixes and re-pushes, loops until CI green + no actionable review threads, then squash-merges with branch delete and removes the worktree. Use after implementation is done and the change is ready to land. Triggers: "ship this change", "ship it…
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
# ship-change End-to-end "land it" pipeline for an OpenSpec change. Runs **after** `openspec-apply` has implemented the code. Orchestrates existing pieces — does not reimplement them. ## Repo conventions (this project) - Base branch: **`develop`**. - Worktree path: **`.worktrees/os-<change>`**, branch **`os/<change>`**. - Remote: `origin` → `github.com:BlackBeltTechnology/pi-agent-dashboard`. - CI scripts: `npx tsx ./scripts/list-recent-runs.ts [--failed]`, `scripts/show-failed-run.ts <run-id>`. - OpenSpec skills resolve from the **parent repo root** when running inside a worktree (per `AGENTS.md`), not the worktree checkout. ## Preconditions (verify, do not assume) 1. `openspec-apply` finished; all **non-QA/manual** tasks are checked. 2. Working tree builds and tests pass (this skill re-verifies). 3. `gh auth status` succeeds; `git remote get-url origin` resolves. Resolve the change name from the worktree dir basename (`os-<change>` → `<change>`) or `openspec list --json`. Announce: "Shipping change: `<change>`". If ambiguous, ask. ## Procedure ### 1. Mark deferrable tasks done (manifest-aware, legacy fallback) …
Read the whole file at its exact version.
How to install
mdr add blackbelttechnology/pi-agent-dashboard/ship-change@sha256:e78ae92871cd3d71The line at the top of this page pins the label v1.1, 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_ycz4ol4i2ziyfg2x)
8 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jul 13, 2026 and Oct 15, 2026, about one every 19 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1 latest | 2026-10-15 | f6de4a9 | 15,980 B | A | view · diff |
| v1.1 | 2026-07-21 | c80a1ca | 15,269 B | A | view · diff |
| v1.1 | 2026-07-17 | a365d0a | 15,284 B | A | view · diff |
| v1.0 | 2026-07-16 | 551684d | 13,202 B | A | view · diff |
| v1.0 | 2026-07-14 | a0fc210 | 11,777 B | A | view · diff |
| v1.0 | 2026-07-13 | ce84be4 | 10,693 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 (15980 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
blackbelttechnology/pi-agent-dashboard · 341 stars · license MIT · pushed 2026-11-06 · branch develop
API
GET https://markdownregistry.com/api/v1/artifacts/art_ycz4ol4i2ziyfg2x GET https://markdownregistry.com/api/v1/resolve?ref=blackbelttechnology/pi-agent-dashboard/ship-change GET https://markdownregistry.com/api/v1/blob/e78ae92871cd3d714b7c9621a99cf2dee6326820cda4f8da8091ecfc8994db8a
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.