analyze-upstream-pr SKILL.md skillA
analyze-upstream-pr from amd-agi/hyperloom is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add amd-agi/hyperloom/analyze-upstream-pr@git:20261020.6cc6611Pins git:20261020.6cc6611 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- amd-agi/hyperloom
- Path
.claude/skills/analyze-upstream-pr/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261020.6cc6611, committed Oct 20, 2026
- First version recorded
- Oct 20, 2026
- Size
- 18,661 bytes
- Repository stars
- 262
- License
- a license file GitHub does not identify
Analyze whether an upstream pull request applies to an AMD/ROCm deployment. Invoke with the PR's repository and number, the target GPU architecture, dtypes and deployment, a local tree and commit of the code the deployment runs (and of the code that selects the changed code, when another repository holds it), and the local patches on top. Collects the PR with check-prior-art's read.sh, states its mechanism and the operating point it was validated at, finds the selection site that decides…
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
<!-- SPDX-FileCopyrightText: 2026 Advanced Micro Devices, Inc. SPDX-License-Identifier: MIT --> # Analyze an upstream pull request for an AMD deployment Written for an agent to execute top to bottom. Every step writes an artifact into `$WORK`, so no step is skipped unseen. An upstream PR was reviewed and measured on its author's platform, so every claim about yours starts as `UNKNOWN` and moves only on the evidence a step names. G numbers are check-prior-art's [gotchas](../check-prior-art/references/gotchas.md). ## Output contract `$WORK/report.md` has five parts, nothing else. **1. Recommendation**: the first row of this table that applies; the last takes every case the others leave. The reader acts on the whole row. | Recommendation | When | Next step | |---|---|---| | `NOT-APPLICABLE -- reverted by <ref>` | a merged revert of the PR survived Step 9; add `, relanded in <ref>` for a merged reland | do not take it; analyze the reland, if any. When Step 4 found the PR and not its revert, the tree carries a change upstream backed out: analyze the revert next | …
Read the whole file at its exact version.
How to install
mdr add amd-agi/hyperloom/analyze-upstream-pr@sha256:d0154794f7bdf287The line at the top of this page pins the label git:20261020.6cc6611, 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_gnvt5m3nz4ladkal)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, all committed on Oct 20, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.6cc6611 latest | 2026-10-20 | 6cc6611 | 18,661 B | A | view · diff |
| git:20261020.01d817a | 2026-10-20 | 01d817a | 17,709 B | A | view · diff |
| git:20261020.1303a4b | 2026-10-20 | 1303a4b | 18,362 B | A | view · diff |
| git:20261020.88bd0be | 2026-10-20 | 88bd0be | 18,522 B | A | view · diff |
| git:20261020.c45a2c6 | 2026-10-20 | c45a2c6 | 18,072 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 (18661 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
amd-agi/hyperloom · 262 stars · license a license file GitHub does not identify · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gnvt5m3nz4ladkal GET https://markdownregistry.com/api/v1/resolve?ref=amd-agi/hyperloom/analyze-upstream-pr GET https://markdownregistry.com/api/v1/blob/d0154794f7bdf2871399e9ff6633ae3830460c6a53086609f6b00bf9bacfbbdf
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.