get-pr-diff-line-mapper
Skill0 starsChanged 9 months agoApache-2.0View on GitHub
Build line-level diff mappings (hunks and line ranges) for files changed in a specific Azure DevOps pull request iteration. Useful for precise inline comment placement and evidence-based review findings.
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-iterationsSkill
- get-pr-review-bundleSkill
- get-pr-threadsSkill
- list-projectsSkill
- list-repositoriesSkill
- post-pr-commentSkill
- reject-prSkill
- reset-feedbackSkill
- update-pr-threadSkill
- wait-for-authorSkill
The file
Files
Get PR Diff-to-Line Mapper
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 | iterationId | Yes | Iteration ID (from get-pr-iterations) |
Examples
go run ./.github/tools/skills-go/cmd/skills-go get-pr-diff-line-mapper myorg MyProject MyRepo 42 3Output
Returns JSON with:
pullRequestId,iterationIdsourceBranch,targetBranchcountfiles[]entries containing:path,changeType,changeTrackingId,isFolderbaseExists,prExistslineMap:hunkCount,totalAdded,totalDeleted,totalContexthunks[]witholdStart,oldLines,newStart,newLines, and per-hunk line totals
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.

