agentleFS
sasky80sasky80/ado-reviewer/.github/skills/update-pr-thread/SKILL.md

update-pr-thread

Skill0 starsChanged 9 months agoApache-2.0View on GitHub

Reply to a comment thread and/or update its status on an Azure DevOps pull request. Use after fixing review findings to respond with a fix description and mark threads as resolved (fixed).

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 a reply is posted, returns JSON with the created comment object.

    line 44
  2. Very specific:

    When status is updated, returns JSON with the updated thread object including id, status, and comments.

    line 45

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

Update PR Thread

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
5threadIdYesComment thread ID
6replyNoReply text (use - to skip and only update status)
7statusNoThread status: active, fixed, closed, byDesign, pending, wontFix

At least one of reply or status must be provided.

Examples

# Reply and mark as fixed
go run ./.github/tools/skills-go/cmd/skills-go update-pr-thread myorg MyProject MyRepo 42 7 "Fixed: refactored to use parameterized queries." fixed

# Reply only (keep thread active)
go run ./.github/tools/skills-go/cmd/skills-go update-pr-thread myorg MyProject MyRepo 42 7 "Working on this, will push a fix shortly."

# Update status only (no reply)
go run ./.github/tools/skills-go/cmd/skills-go update-pr-thread myorg MyProject MyRepo 42 7 - fixed

Output

When a reply is posted, returns JSON with the created comment object. When status is updated, returns JSON with the updated thread object including id, status, and comments.

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.