post-pr-review
Skill2 starsChanged 7 months agoNo licenceView on GitHub
Post a completed code review to a GitHub PR as file-anchored inline comments. Use whenever the user says "post the review", "submit the review", "把评审发到PR", "把review发上去", "把 comment post 上去", "提交 PR 评审", "提 PR review", or confirms publishing after a `/review-pr` / `/pr-review-toolkit:review-pr` analysis — even when they don't explicitly name the tool. Default to this skill instead of `gh pr review --comment` or `gh pr comment`; those post unanchored comments and have been rejected by the user ("你没有follow claude.md的要求吗？需要post到 PR固定的位置"). Sharp edges: abbreviated commit SHA gets a misleading "Variable $commitOID invalid value" error; local HEAD drifts after force-push and triggers "commit_id is not part of the pull request"; `json.load(sys.stdin)` on `gh api` output chokes on error-path suffixes.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- kameyama/claude_skillstheir own version, first seen Oct 25, 2026
- kaiohenricunha/dotbabeltheir own version, first seen Oct 17, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- kaiohenricunha/dotbabel★ 0same name
- kameyama/claude_skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- cuda-cpp-kernelSkill
- cute-dsl-kernelSkill
- cutlass-cpp-kernelSkill
- nvfp4-conversionSkill
- sglang-ci-monitorSkill
- swe-bench-proSkill
- swe-benchSkill
- terminal-bench-harborSkill
- vast-ai-cliSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — 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.