dev-flow

- Current branch: !`git branch --show-current`

Check out an Azure DevOps PR's source branch locally

Complete (merge) the Azure DevOps PR for current branch

Commit changes, push branch, and create Azure DevOps PR in one workflow

List Azure DevOps PRs (mine by default, or all with "all" argument)

Code review an Azure DevOps pull request (read-only)

Set Azure DevOps work item to Code Review

Set Azure DevOps work item to Active

Triage an Azure DevOps work item with Confluence context

- Current git status: !`git status`

Download raw insights data from last collection date until today

Generate daily codebase activity summary from Azure DevOps, git, and optionally Confluence

Generate interactive dashboard from insights data

Generate weekly codebase activity summary from Azure DevOps, git, and optionally Confluence

Code review current branch against base (master/main)

Generate implementation spec from triage output

Triage manually pasted requirements or specifications

This skill should be used when working with Azure DevOps from the command line. Trigger when user mentions az devops, az repos, az pipelines, az boards, or asks about managing PRs, work items, pipelines, or repositories in Azure DevOps. Also trigger for questions about Azure DevOps CLI setup, authentication, or querying work items.

Manage Azure DevOps PR comments - post new code comments, read and assess existing threads. Trigger when user asks to add/post a comment on a PR, review PR feedback, or check PR comment status.

Core code review logic. Trigger when invoked by review commands. Do not trigger directly from user requests - use /df:review or /df:azdo:review instead.

Generate daily and weekly codebase activity summaries from Azure DevOps (PRs, work items), local git commits, and Confluence. Use when asked about "what happened", "codebase activity", "team summary", "pr summary", or to understand what's going on in a large codebase.

Methodology reference for generating implementation specs. Invoked via /df:spec command.

This skill should be used when the user wants to triage an issue, review a specification, or assess requirements completeness. Trigger when user mentions "triage", "review this spec", "is this requirement complete", "what questions should I ask", or provides a description/acceptance criteria that needs evaluation before implementation. The skill analyzes input against the codebase and project documentation to surface implicit requirements and generate clarifying questions.