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).
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
- post-pr-commentSkill
- reject-prSkill
- reset-feedbackSkill
- 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 44
When a reply is posted, returns JSON with the created comment object.
- Very specific: line 45
When status is updated, returns JSON with the updated thread object including id, status, and comments.
≈ “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
Update PR Thread
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 | threadId | Yes | Comment thread ID |
| 6 | reply | No | Reply text (use - to skip and only update status) |
| 7 | status | No | Thread 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 - fixedOutput
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.
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.

