agentleFS
sasky80sasky80/ado-reviewer/.github/skills/post-pr-comment/SKILL.md

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.

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
  1. Very specific:

    When posting structured review findings, avoid literal \n\n sequences in comment text.

    line 39
  2. Very specific:

    Use a single HTML line break (<br/>) between sections, for example:

    line 40

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Post PR Comment

Platform Note

  • Clean-install path: use the Go command from .github/tools/skills-go.

Arguments

#NameRequiredDescription
1organizationYesAzure DevOps organization
2projectYesProject name or ID
3repositoryIdYesRepository name or ID
4pullRequestIdYesPull request ID
5filePathYesRepository-relative file path for inline comment (canonical form like /src/app.js; use - for a general comment)
6lineYesLine number for inline comment (use 0 for general comments)
7commentYesComment 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.