pr
Skill0 starsChanged 3 months agoMITView on GitHub
Manage Pull Requests - create, update description, add wiki links. Use for all PR operations in Azure DevOps.
- Commits and pushes
In this repository27 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- buildSkill
- cleanup-worktreeSkill
- db-querySkill
- db-searchSkill
- dd-errorsSkill
- devops-wiki-updateSkill
- devops-workitem-createSkill
- devops-workitem-readSkill
- devops-workitem-updateSkill
- finalize-taskSkill
- find-codeSkill
- merge-mainSkill
- panel-review-fixSkill
- panel-reviewSkill
- rebase-mainSkill
- starttaskSkill
- testSkill
- ask-codexSkill
- ask-geminiSkill
- councilSkill
- dailySkill
- find-sessionSkill
- merged-prsSkill
- mm-notifySkill
- optimize-promptSkill
- qSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 47
Check if branch is pushed to remote, if not push it: git push -u origin {branch}
- Distinctive: line 48
Create PR via POST with:
- Very specific: line 60
Default/prepend: Add content at beginning
- Very specific: line 68
Remove existing ## Documentation section if present
- Very specific: line 107
Always use -UseDefaultCredentials for Windows auth
- Distinctive: line 110
When updating, preserve existing description content unless explicitly replacing
- Distinctive: line 111
Use PowerShell scripts saved to temp files to avoid escaping issues with complex commands
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Pull Request Management
Command: /pr $ARGUMENTS
Commands
| Command | Description | Example |
create | Create new PR from current branch | /pr create "My PR Title" |
update | Update PR description | /pr update "New description content" |
wiki | Add wiki documentation link to PR | /pr wiki "Title|URL" or /pr wiki URL |
info | Show current branch's PR info | /pr info |
Azure DevOps Configuration
- Server: https://devops.example.com/
- Project: MyProject (ID:
<PROJECT_ID>) - Repository: Payments (ID:
<REPO_ID>) - Auth: Windows Integrated Security (UseDefaultCredentials)
API Endpoints
Base URL: https://devops.example.com/DefaultCollection/MyProject/_apis/git/repositories/<REPO_ID>| Operation | Method | Endpoint |
| Get PR by branch | GET | /pullrequests?searchCriteria.sourceRefName=refs/heads/{branch}&api-version=6.0 |
| Get PR by ID | GET | /pullrequests/{id}?api-version=6.0 |
| Create PR | POST | /pullrequests?api-version=6.0 |
| Update PR | PATCH | /pullrequests/{id}?api-version=6.0 |
Your Task
Parse $ARGUMENTS and execute the appropriate command:
/pr create "Title" or /pr create "Title" "Description"
- Get current branch name:
git rev-parse --abbrev-ref HEAD - Check if branch is pushed to remote, if not push it:
git push -u origin {branch} - Create PR via POST with:
sourceRefName:refs/heads/{current-branch}targetRefName:refs/heads/maintitle: from argumentsdescription: from arguments (optional)
- Return PR URL:
https://devops.example.com/DefaultCollection/MyProject/_git/Payments/pullrequest/{id}
/pr update "content" or /pr update prepend "content" or /pr update append "content"
- Get current branch name
- Find PR for current branch via GET search
- Get current description
- Update description:
- Default/
prepend: Add content at beginning append: Add content at endreplace: Replace entire description
- Default/
- PATCH the PR with new description
/pr wiki "Title|URL" or /pr wiki URL
- Parse wiki link - if no
|, use "Documentation" as title - Find PR for current branch
- Remove existing
## Documentationsection if present - Prepend new documentation section:
## Documentation - [Title](URL) - PATCH the PR
/pr info
- Get current branch name
- Find PR for current branch
- Display: PR ID, Title, Status, URL, Description preview
PowerShell Template for API Calls
$repoId = "<REPO_ID>"
$baseUrl = "https://devops.example.com/DefaultCollection/MyProject/_apis/git/repositories/$repoId"
# GET request
Invoke-RestMethod -Uri "$baseUrl/pullrequests?searchCriteria.sourceRefName=refs/heads/$branch&api-version=6.0" -UseDefaultCredentials
# PATCH request
$body = @{ description = $newDesc } | ConvertTo-Json -Depth 5
Invoke-RestMethod -Uri "$baseUrl/pullrequests/$prId`?api-version=6.0" -Method Patch -Body $body -ContentType "application/json" -UseDefaultCredentials
# POST request (create)
$body = @{
sourceRefName = "refs/heads/$branch"
targetRefName = "refs/heads/main"
title = $title
description = $description
} | ConvertTo-Json -Depth 5
Invoke-RestMethod -Uri "$baseUrl/pullrequests?api-version=6.0" -Method Post -Body $body -ContentType "application/json" -UseDefaultCredentialsImportant
- Always use
-UseDefaultCredentialsfor Windows auth - PR URL format:
https://devops.example.com/DefaultCollection/MyProject/_git/Payments/pullrequest/{id} - Wiki link format supports both
Title|URLand justURL - When updating, preserve existing description content unless explicitly replacing
- Use PowerShell scripts saved to temp files to avoid escaping issues with complex commands
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.

