get-pr-threads
Skill0 starsChanged 9 months agoApache-2.0View on GitHub
Fetch all comment threads on an Azure DevOps pull request (review comments, discussions, system messages) and use it to see existing reviewer feedback before writing your own review.
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
- list-projectsSkill
- list-repositoriesSkill
- post-pr-commentSkill
- reject-prSkill
- reset-feedbackSkill
- update-pr-threadSkill
- wait-for-authorSkill
The file
Files
Get PR Threads
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 | statusFilter | No | Keep only threads with this status (e.g. active, fixed, closed). Default: all statuses. |
| 6 | excludeSystem | No | true to remove system-generated threads (vote changes, ref updates). Default: false. |
Examples
# All threads (default)
go run ./.github/tools/skills-go/cmd/skills-go get-pr-threads myorg MyProject MyRepo 42
# Only active, non-system threads
go run ./.github/tools/skills-go/cmd/skills-go get-pr-threads myorg MyProject MyRepo 42 active true
# All statuses but exclude system threads
go run ./.github/tools/skills-go/cmd/skills-go get-pr-threads myorg MyProject MyRepo 42 "" trueOutput
Returns JSON with a value array of thread objects, each containing comments, threadContext (file path and line range), 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.

