analyze-upstream-pr
Skill272 starsChanged 4 days agoLicence not identifiedView on GitHub
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 whether the deployment runs the changed code, checks the tree with the inclusion probe, runs check-prior-art for other PRs that carry the change, checks the diff against the target commit, refutes every claim once, and writes one recommendation with its evidence. Reads GitHub, never writes to it, and never runs a benchmark.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- check-prior-artSkill
- review-prSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 1 is distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.