engineering-pr-review SKILL.md skillA
engineering-pr-review from collectiveai-team/botica is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add collectiveai-team/botica/engineering-pr-review@git:20261020.7ea4422Pins git:20261020.7ea4422 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- collectiveai-team/botica
- Path
skills/engineering/engineering-pr-review/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261020.7ea4422, committed Oct 20, 2026
- First version recorded
- Oct 13, 2026
- Size
- 2,378 bytes
- Repository stars
- 9
- License
- a license file GitHub does not identify
PR gate that runs botica, reviews the diff with the upstream code-review skill and writes the body with the pr skill, before creating, opening, updating, or marking a pull request ready. Use when an agent is about to create a PR, update a PR, publish a branch, request review, or summarize PR readiness.
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
# Engineering PR Review Run this before creating, opening, updating, or marking a PR ready. This skill is a workflow and states no rule of its own: the rules are in botica, and the review procedure is the one of the upstream `code-review` skill. ## 1. Context 1. Pin the target branch and capture the diff: `git diff <target>...HEAD` and `git log <target>..HEAD --oneline`. 2. Read the judgment rules of `AGENTS.md` (between `<!-- botica:rules -->` and `<!-- /botica:rules -->`), `GLOSSARY.md` and the ADRs under `docs/adr/` that the diff touches. ## 2. Deterministic rules Run `botica lint` on the changed files (`botica lint $(git diff --name-only <target>...HEAD)`), or the hooks of the repository with `uvx prek run --from-ref <target> --to-ref HEAD`. Fix each finding of severity error. A warning is fixed only if the diff introduced it. For a finding you do not understand, run `botica explain <slug>`. When the rule or its standard cites a topic, `botica refs show <slug>` prints the code it expects. ## 3. Review Invoke the upstream `code-review` skill against `<target>`. Its Standards axis reads the documents …
Read the whole file at its exact version.
How to install
mdr add collectiveai-team/botica/engineering-pr-review@sha256:0e0da12af401c79eThe line at the top of this page pins the label git:20261020.7ea4422, 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_bcn2bla54bo37ur2)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 13, 2026 and Oct 20, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.7ea4422 latest | 2026-10-20 | 7ea4422 | 2,378 B | A | view · diff |
| git:20261020.a157858 | 2026-10-20 | a157858 | 2,399 B | A | view · diff |
| git:20261018.e05a5c3 | 2026-10-18 | e05a5c3 | 4,359 B | A | view · diff |
| git:20261013.4072684 | 2026-10-13 | 4072684 | 4,232 B | A | view · diff |
| git:20261013.8c5024b | 2026-10-13 | 8c5024b | 4,231 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 (2378 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
collectiveai-team/botica · 9 stars · license a license file GitHub does not identify · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bcn2bla54bo37ur2 GET https://markdownregistry.com/api/v1/resolve?ref=collectiveai-team/botica/engineering-pr-review GET https://markdownregistry.com/api/v1/blob/0e0da12af401c79ee021bcb67825097635e0554457d40b02046c21b2d572a1b1
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.