pr-workflow skillA
pr-workflow is agent-read markdown (skill) from office-kit/pptx: Use when opening a pull request. Covers branch naming, commit hygiene, PR title and body conventions, and what must be true before a PR leaves draft. Invoked when the user says "open a PR", "create a PR", "submit", or asks to push and PR a branch..
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
# PR workflow The shape of a PR communicates the change to maintainers and to a future archaeologist reading `git log`. Get it right at write time — the cost of fixing a confusing PR later is much higher than getting it right once. ## Before you open the PR 1. **Branch is up to date with the base.** Rebase onto `main` (or whatever the base is) so the PR diff is clean. Don't merge `main` into your feature branch as a habit; rebase. 2. **All quality gates pass locally.** Use the `run-check-and-test` skill — typecheck, lint, format, test, build. CI will catch you if you skip this; just do it locally. 3. **Each commit is meaningful.** Squash WIP commits. The git log should read as a sequence of "I did this, then I did this, then I did this," not "fix typo / fix again / really fix this time." 4. **The change has an issue or design discussion to point at**, unless it's trivially small (typo, comment, single-line bugfix). For non-trivial features, the discussion happens _before_ the PR, not in PR review. ## Branch name ``` <type>/<short-slug> ``` Conventional types match the commit prefixes below: `feat`, `fix`, `refactor`, `docs`, …
Read the whole file at its exact version.
How to install
mdr add office-kit/pptx/pr-workflow@git:20260514.7b45fd7mdr add office-kit/pptx/pr-workflow@sha256:9ca6c5b1c6a1d808Pin 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_eippahjbxvq6slsc)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260514.7b45fd7 latest | 2026-05-14 | 7b45fd7 | 7,495 B | A | view · diff |
| git:20260514.f87e12d | 2026-05-14 | f87e12d | 7,592 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 (7495 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
office-kit/pptx · 14 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_eippahjbxvq6slsc GET https://markdownregistry.com/api/v1/resolve?ref=office-kit/pptx/pr-workflow GET https://markdownregistry.com/api/v1/blob/9ca6c5b1c6a1d808a1405bc76c9111b34332cf8cc9b7bc537197ee5384ac0273
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.