pr-comments
Manage Azure DevOps PR comments — post new code comments, read and assess existing threads. Trigger when user says "/df:pr-comments", asks to add/post a comment on a PR, review PR feedback, or check PR comment status. Input is PR id/URL, or empty to use current branch's PR.
What this skill does
# PR Comments (Azure DevOps)
Read, assess, and post code-level comments on Azure DevOps pull requests.
## API Reference
The `az repos pr` CLI does not support PR threads. Use `az devops invoke` for all thread operations.
Detect `project` and `repositoryId` from git remote or `az devops configure --list`.
### Fetch all threads
```bash
az devops invoke \
--area git \
--resource pullRequestThreads \
--route-parameters \
project=<project> \
repositoryId=<repo-name-or-id> \
pullRequestId=<pr-id> \
-o json
```
### Create thread on file/line
```bash
az devops invoke \
--area git \
--resource pullRequestThreads \
--route-parameters \
project=<project> \
repositoryId=<repo-name-or-id> \
pullRequestId=<pr-id> \
--http-method POST \
--in-file <(cat <<'EOF'
{
"comments": [
{
"parentCommentId": 0,
"content": "Comment text (markdown supported)",
"commentType": 1
}
],
"threadContext": {
"filePath": "/path/to/file.vue",
"rightFileStart": { "line": 31, "offset": 1 },
"rightFileEnd": { "line": 38, "offset": 1 }
},
"status": 1
}
EOF
)
```
**Thread status:** 0 = unknown, 1 = active, 2 = fixed, 3 = won't fix, 4 = closed, 5 = by design, 6 = pending
**Line targeting:**
- `rightFileStart`/`rightFileEnd` - new code (most common)
- `leftFileStart`/`leftFileEnd` - deleted code
- Single line: same start and end
- Omit `threadContext` entirely for a general (non-file) comment
### Reply to existing thread
```bash
az devops invoke \
--area git \
--resource pullRequestThreadComments \
--route-parameters \
project=<project> \
repositoryId=<repo-name-or-id> \
pullRequestId=<pr-id> \
threadId=<thread-id> \
--http-method POST \
--in-file <(cat <<'EOF'
{"content": "Reply text"}
EOF
)
```
**Verify success:** Response contains `"id":` field. Do NOT retry if first attempt returns valid JSON with an ID.
## Posting: Comment Text Style
When posting review comments to PRs, be concise:
- State the issue directly - no header, no title, no label prefix
- File context is already visible in the PR UI, don't repeat it
- No dramatic impact predictions ("will cause X", "breaks Y")
- No bold wrapping of the whole message
- One sentence is ideal, two max
```
# Good
Orphaned `</a>` tags after refactoring.
# Good
`useI18n()` not called - `t` will be undefined.
# Bad
**C1. Broken HTML in PharmacistsCarousel**
Orphaned `</a>` tags and bare HTML attributes not attached to any element.
**Will cause template compilation error or mangled rendering.**
```
## Assessing: Reading Existing Comments
### Parse threads
Extract code comments (threads with file context):
```bash
jq '[.value[] | select(.threadContext.filePath) | select(.status == "closed" | not) | {
id: .id,
file: .threadContext.filePath,
line: .threadContext.rightFileStart.line,
status: .status,
comment: .comments[0].content,
author: .comments[0].author.displayName
}]'
```
### Assess each comment
For each active/pending comment:
1. Read the file at the specified path
2. Check the referenced line (account for line shifts from subsequent commits)
3. Determine status:
- Addressed - code changed to address the feedback
- Partially addressed - some changes, not fully resolved
- Not addressed - original code unchanged
- Unable to assess - file deleted, heavily refactored, or comment unclear
4. Provide brief assessment (1-2 sentences)
### Determine PR ID
Priority:
1. Explicit argument
2. Auto-detect from current branch:
```bash
az repos pr list --source-branch "$(git branch --show-current)" --status active --query '[0].pullRequestId' -o tsv
```
3. Ask user
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.