agentleFS
sasky80sasky80/ado-reviewer/.github/skills/get-pr-changes/SKILL.md

get-pr-changes

Skill0 starsChanged 9 months agoApache-2.0View on GitHub

Fetch the list of file changes for a specific iteration of an Azure DevOps pull request. Shows which files were added, edited, or deleted. Requires an iteration ID obtained from get-pr-iterations.

The file

Files
SKILL.md

Get PR Changes

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
5iterationIdYesIteration ID (from get-pr-iterations)

Examples

go run ./.github/tools/skills-go/cmd/skills-go get-pr-changes myorg MyProject MyRepo 42 3

Output

Returns JSON with changeEntries listing files with their changeType (add, edit, delete) and item.path.

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.