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.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: sasky80-ado-reviewer-post-pr-comment3description: Post PR Comment4---56# Post PR Comment78## Platform Note910- Clean-install path: use the Go command from `.github/tools/skills-go`.1112## Arguments1314| # | Name | Required | Description |15|---|------|----------|-------------|16| 1 | organization | Yes | Azure DevOps organization |17| 2 | project | Yes | Project name or ID |18| 3 | repositoryId | Yes | Repository name or ID |19| 4 | pullRequestId | Yes | Pull request ID |20| 5 | filePath | Yes | Repository-relative file path for inline comment (canonical form like `/src/app.js`; use `-` for a general comment) |21| 6 | line | Yes | Line number for inline comment (use `0` for general comments) |22| 7 | comment | Yes | Comment text (supports Markdown) |2324## Examples2526```bash27# Inline comment on a specific file and line (canonical repository path)28go run ./.github/tools/skills-go/cmd/skills-go post-pr-comment myorg MyProject MyRepo 42 /src/app.js 15 "Consider using const here."2930# General PR-level comment31go run ./.github/tools/skills-go/cmd/skills-go post-pr-comment myorg MyProject MyRepo 42 - 0 "Overall the code looks good."32```3334## Formatting Note3536When posting structured review findings, avoid literal `\n\n` sequences in comment text.37Use a single HTML line break (`<br/>`) between sections, for example:3839```text40🟠 Major | Security<br/>Description: ...<br/>Recommendation: ...41```4243## Output4445Returns JSON with the created thread object including `id`, `comments`, and `status`.4647---48> Converted and distributed by [TomeVault](https://tomevault.io/claim/sasky80) — claim your Tome and manage your conversions.49<!-- tomevault:4.0:skill_md:2026-04-15 -->
Run npx skillmds@latest add tomevault-io/sasky80-ado-reviewer-post-pr-comment in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Post PR Comment It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.
tomevault-io