post-pr-comment
Skill0 starsChanged 9 months agoApache-2.0View on GitHub
Create a comment thread on an Azure DevOps pull request. Can post inline comments on a specific file and line, or general PR-level comments. Use after completing a code review to post findings back to the PR.
In this repository21 other files it gives its agents.
- accept-prSkill
- approve-with-suggestionsSkill
- check-deprecated-dependenciesSkill
- get-commit-diffsSkill
- get-file-contentSkill
- get-github-advisoriesSkill
- get-multiple-filesSkill
- get-pr-changed-filesSkill
- get-pr-changesSkill
- get-pr-dependency-advisoriesSkill
- get-pr-detailsSkill
- get-pr-diff-line-mapperSkill
- get-pr-iterationsSkill
- get-pr-review-bundleSkill
- get-pr-threadsSkill
- list-projectsSkill
- list-repositoriesSkill
- reject-prSkill
- reset-feedbackSkill
- update-pr-threadSkill
- wait-for-authorSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 39
When posting structured review findings, avoid literal \n\n sequences in comment text.
- Very specific: line 40
Use a single HTML line break (<br/>) between sections, for example:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Post PR Comment
Platform Note
- Clean-install path: use the Go command from
.github/tools/skills-go.
Arguments
| # | Name | Required | Description |
| 1 | organization | Yes | Azure DevOps organization |
| 2 | project | Yes | Project name or ID |
| 3 | repositoryId | Yes | Repository name or ID |
| 4 | pullRequestId | Yes | Pull request ID |
| 5 | filePath | Yes | Repository-relative file path for inline comment (canonical form like /src/app.js; use - for a general comment) |
| 6 | line | Yes | Line number for inline comment (use 0 for general comments) |
| 7 | comment | Yes | Comment text (supports Markdown) |
Examples
# Inline comment on a specific file and line (canonical repository path)
go run ./.github/tools/skills-go/cmd/skills-go post-pr-comment myorg MyProject MyRepo 42 /src/app.js 15 "Consider using const here."
# General PR-level comment
go run ./.github/tools/skills-go/cmd/skills-go post-pr-comment myorg MyProject MyRepo 42 - 0 "Overall the code looks good."Formatting Note
When posting structured review findings, avoid literal \n\n sequences in comment text.
Use a single HTML line break (<br/>) between sections, for example:
🟠 Major | Security<br/>Description: ...<br/>Recommendation: ...Output
Returns JSON with the created thread object including id, comments, and status.
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.

