From Git Commits to Azure DevOps Tasks in Seconds: The AI-Powered Workflow Every Developer Needs

You've just spent the entire day deep in development - implementing features, fixing bugs, refactoring code. You've made 15 git commits on your current user story. Now it's 5 PM, and you need to log your work in Azure DevOps for tomorrow's standup. But here's the problem: you can barely remember what you did this morning, let alone the specific details of each task you completed.

Sound familiar? For developers working in Azure DevOps, this end-of-day ritual is painful. You dig through git logs, try to remember which commits represent distinct tasks, manually create task work items, copy-paste commit messages, and hope you didn't miss anything important. The process takes 5-10 minutes every single day - and the finer details still get lost.

I built the ai-ado plugin to solve this exact problem. Part of my open-source Claude Code plugin marketplace, it transforms Azure DevOps work item management from a manual chore into an automated workflow. Now, with a single command like /ado-log-story-work, I can create detailed task work items - complete with git commit detection, AI-generated descriptions, and automatic hour tracking - in under 30 seconds. Here's how it works and why every Azure DevOps developer needs this workflow.

The Problem: Losing Track of Development Details#

Large development tasks often span multiple days and involve dozens of small changes. Each change is important - bug fixes, refactoring, new features, configuration updates - but they're easy to forget when it's time to log work.

What Gets Lost#

When you're manually logging work at the end of the day, critical details slip through the cracks:

• Specific implementation details: Which API endpoints did you create? What validation logic did you add?
• Bug fixes: That authentication edge case you spent an hour fixing - did you log it?
• Refactoring work: Code cleanup and optimization doesn't always make it into work logs
• Configuration changes: Environment setup, dependency updates, build script modifications
• Git commit context: The exact files changed and why they were changed
• Time estimates: How long did each sub-task actually take?

These details matter. During standups, stakeholders want to know what you accomplished. During sprint retrospectives, teams need accurate data. During performance reviews, you need a record of your work. But when you're relying on memory and manual processes, the details vanish.

The Manual Azure DevOps Process#

Here's what end-of-day work logging typically looks like without automation:

1. Review git log: Run git log --oneline to see what you committed
2. Match commits to stories: Figure out which commits belong to which user stories
3. Open Azure DevOps: Navigate to your project in the web browser
4. Find the user story: Search for the correct work item ID
5. Create a task: Click through the UI to create a new task work item
6. Fill in fields: Manually type title, description, copy-paste commit info
7. Set hours: Estimate completed hours, set remaining work to 0
8. Link to parent: Ensure the task is linked to the correct user story
9. Repeat: Do this for every significant piece of work from the day

For a typical day with 3-5 distinct tasks, this process takes 5-10 minutes. Multiply that by 5 days a week, and you're spending over an hour every week just logging work you've already completed.

The Solution: Claude Code Plugin Ecosystem#

Claude Code's plugin system (October 2025) lets developers extend Claude with custom commands, specialized agents, and automated workflows. I've built an open-source plugin marketplace containing productivity tools I use daily - and the ai-ado plugin is one of the most impactful.

The Plugin Marketplace#

The marketplace includes four powerful plugins, all designed to automate common developer workflows:

Automated security auditing with OWASP Top 10 coverage (8 hours → 3 minutes)

ai-performance: Performance bottleneck detection and optimization guidance

ai-git: Intelligent git automation with commit message generation

ai-ado: Azure DevOps work item automation with git commit detection and AI-powered generation

Each plugin solves a specific workflow problem. Together, they form a comprehensive automation toolkit that saves hours every week. The ai-ado plugin specifically targets the Azure DevOps work item management bottleneck.

Before & After: The Transformation#

Let's compare the manual process with the ai-ado automated workflow using a real-world scenario: logging completed development work at the end of the day.

Scenario: End-of-Day Work Logging#

You've been working on User Story #12345: "Implement user authentication system." Throughout the day, you made commits for JWT token validation, password hashing, and session management. Now you need to log this work in Azure DevOps.

BEFORE: Manual Process (5-10 minutes)#

# Step 1: Check what you did today
git log --oneline --since="9am"
# Output:
abc1234 Add JWT token validation
def5678 Implement password hashing with bcrypt
ghi9012 Create session management endpoints

# Step 2: Try to remember which commits go together
# (mentally group commits by feature/task)

# Step 3: Open Azure DevOps in browser
# Navigate to project → Boards → Work Items

# Step 4: Search for User Story #12345
# Click to open work item details

# Step 5: Click "Add link" → "New item" → "Task"

# Step 6: Fill in the form manually
# Title: "Implement JWT token validation and password hashing"
# Description: Copy-paste commit messages, add context
# Original Estimate: 4 hours
# Completed Work: 4 hours
# Remaining Work: 0 hours
# State: Closed

# Step 7: Save the task

# Step 8: Repeat for session management work
# Create another task, fill in fields again...

# Step 9: Double-check everything is linked correctly

# Total time: 5-10 minutes
# Details lost: Specific file changes, implementation nuances
# Context switches: 3-4 times between terminal, browser, code

Notice the friction: multiple tool switches, manual data entry, reliance on memory, and time-consuming UI navigation. Critical details like file paths and specific implementation choices aren't captured.

AFTER: AI-ADO Automated Workflow (30 seconds)#

# Step 1: Run the command
/ado-log-story-work

# Step 2: Answer prompts
# User Story ID: 12345
# Mode: AI
# Description: "Implemented JWT authentication - see commit abc1234"

# ✨ AI detects commit abc1234 and retrieves details
# ✨ AI generates title and description with commit context
# ✨ You review and confirm the generated content

# Step 3: Provide hours
# Completed hours: 4

# ✨ Task #12389 created and linked to User Story #12345!
# ✨ View: https://dev.azure.com/org/project/_workitems/edit/12389

# Total time: 30 seconds
# Details captured: Commit hash, files changed, implementation notes
# Context switches: 0 (everything in terminal)

The difference is dramatic. No browser required. No manual typing. No lost details. AI detects your git commit, retrieves the context, generates professional work item content, and creates the task - all while you stay in your terminal.

Key Features: What Makes This Plugin Powerful#

The ai-ado plugin provides five core commands for complete Azure DevOps work item lifecycle management and more are coming soon. Each command is designed to eliminate manual work while maintaining professional quality.

1. Git Commit Hash Detection#

The /ado-log-story-work command includes intelligent git commit detection - one of its most powerful features.

• Automatically detects git commit hashes in your description (both full and short SHA)
• Supports common patterns: "commit abc123", "see commit 1a2b3c4", "hash: def456789"
• Runs git show to retrieve commit message and file changes
• Includes commit details in the generated task description
• Non-blocking: continues without commit context if git lookup fails

• Full commit hash (for traceability)
• Short commit hash (for readability)
• Commit message
• List of files changed
• Implementation context from commit

Example generated task description:

"Implemented JWT token validation with expiration handling.

Related commit: abc1234 (abc123456789abcdef123456789abcdef12345678)
Files changed:

- src/auth/jwt.service.ts
- src/middleware/auth.middleware.ts
- tests/auth/jwt.test.ts

Added token signing, verification, and refresh logic with proper error handling."

This feature ensures you never lose the connection between your code changes and your work items. During code reviews or retrospectives, you can trace exactly what was done and where.

2. AI-Powered Work Item Generation#

All work item commands support AI generation mode, which creates professional content from simple descriptions.

• Features: Professional titles and comprehensive descriptions
• User Stories: Titles, persona statements (As a... I want to... so that...), background, acceptance criteria (Given/When/Then format)
• Tasks: Descriptive titles focused on work to be done
• Work logs: Detailed descriptions with git commit context and implementation notes

• Follows your organization's naming conventions from CLAUDE.md
• Professional formatting with proper HTML structure
• Consistent quality across all work items
• Review-and-confirm workflow (every field shown before creation)
• Context-aware generation based on parent work items

3. Microsoft Azure DevOps MCP Integration#

The plugin integrates with the official Microsoft Azure DevOps MCP (Model Context Protocol) server, enabling seamless communication between Claude Code and your Azure DevOps organization.

• Direct API access to Azure DevOps work items
• Secure authentication via Microsoft account (browser-based OAuth)
• Create, read, and update work items programmatically
• Establish parent-child relationships automatically
• Set field values (hours, state, area path, iteration) via API

The /ado-init command can optionally create a .mcp.json configuration file with OS-aware settings (Windows uses cmd /c npx, Linux/Mac uses npx). The MCP server runs via npx - no global installation required.

// .mcp.json (Windows example)
{
  "mcpServers": {
    "ado": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "@azure-devops/mcp", "your-organization"]
    }
  }
}

First-time use opens a browser for Microsoft authentication. Credentials must match your Azure DevOps organization access.

4. Placeholder Task Hour Subtraction#

A unique feature for teams that pre-allocate hours: when logging completed work, you can optionally subtract hours from a placeholder task.

Many teams create placeholder tasks at the start of a sprint with estimated hours (e.g., "Development - 40 hours"). As you complete specific sub-tasks, you want to subtract those hours from the placeholder to track remaining capacity.

• After creating the completed work task, you're prompted: "Subtract hours from a placeholder task?"
• If yes, provide the placeholder task ID
• AI retrieves current placeholder values (Original Estimate, Remaining Work)
• AI calculates new values (subtracts your completed hours)
• AI updates the placeholder task automatically
• Displays before/after comparison in success message

Example output:

Task #12389 created successfully!
Completed hours: 4
View: https://dev.azure.com/org/project/_workitems/edit/12389

Placeholder Task #12350 updated:
Original Estimate: 40h → 36h
Remaining Work: 40h → 36h
View: https://dev.azure.com/org/project/_workitems/edit/12350

This feature keeps your sprint burndown charts accurate and ensures capacity planning stays synchronized with actual work.

5. Complete Work Item Hierarchy Management#

Beyond logging work, the plugin provides commands for the full Azure DevOps work item lifecycle:

/ado-init: Initialize Azure DevOps configuration

• Collects organization, project, team settings
• Configures default Area Path and Iteration Path
• Sets up naming conventions (decimal notation or descriptive)
• Creates work item guidelines in CLAUDE.md
• Optionally creates .mcp.json for MCP server setup

/ado-create-feature: Create Feature work items

• AI or manual mode
• Professional title and high-level description
• Top-level hierarchy work item

/ado-create-story: Create User Story work items

• AI generates persona statements and acceptance criteria
• Linked as child of Feature
• Story Points estimation

/ado-create-task: Create Task work items

• AI generates task titles
• Linked as child of User Story
• Hour estimates (Original Estimate = Remaining Work)

/ado-log-story-work: Log completed work

• Git commit detection and context
• AI-generated descriptions
• Hours already completed (Remaining Work = 0)
• Optional placeholder hour subtraction

Together, these commands cover the entire work item lifecycle - from sprint planning to daily work logging to retrospective tracking.

Installation & Setup#

Getting started with this plugin takes less than 5 minutes. It is part of my open-source Claude Code plugin marketplace, which includes ai-security (read blog), ai-performance, and ai-git plugins as well.

Prerequisites#

• Node.js 20+: Required for npx to run the Azure DevOps MCP server (check with node --version)
• Azure DevOps access: Valid account with permissions to create work items
• Claude Code: Plugin-capable build (October 2025 or later)

Installation Steps#

# Step 1: Add the plugin marketplace
/plugin marketplace add charlesjones-dev/claude-code-plugins-dev

# Step 2: Install the ai-ado plugin
/plugin install ai-ado@claude-code-plugins-dev

# Step 3: Navigate to your project directory
cd /path/to/your/project

# Step 4: Initialize Azure DevOps configuration
/ado-init

# You'll be prompted for:
# - Organization name (e.g., "contoso")
# - Project name (e.g., "MyProject")
# - Team name (e.g., "Development Team")
# - Area Path (e.g., "MyProject\Team\Development")
# - Iteration Path (e.g., "MyProject\Sprint 1")
# - Use decimal notation? (Yes/No)
# - Create .mcp.json? (Yes)
# - Operating System? (Windows or Linux/Mac)

# ✅ CLAUDE.md and .mcp.json are configured!

# Step 5: Restart Claude Code to apply MCP settings

# Step 6: Start using the commands!
/ado-create-feature
/ado-create-story
/ado-create-task
/ado-log-story-work

First-Time Authentication#

The first time you use an Azure DevOps command, the MCP server will open a browser window for Microsoft authentication. Sign in with the account that has access to your Azure DevOps organization. Credentials are cached for future sessions.

The Broader Plugin Ecosystem#

The ai-ado plugin is part of my comprehensive automation toolkit. Here's how the plugins work together to maximize productivity:

ai-security: Automated Security Auditing#

Transforms 8-hour manual security audits into 3-minute automated processes with OWASP Top 10 coverage, reproducible reports, and compliance documentation. Read the full article on ai-security.

Key commands: /security-init, /security-audit

Use case: Run security audits before production deployments, after adding authentication features, or during quarterly reviews.

ai-performance: Performance Optimization#

Identifies performance bottlenecks, N+1 query issues, and optimization opportunities with automated analysis and remediation guidance.

Key commands: /performance-audit

Use case: Optimize slow endpoints, identify database query issues, analyze bundle sizes.

ai-git: Intelligent Git Automation#

Analyzes code changes and generates professional commit messages that match your repository's style and conventions.

Use case: Maintain consistent commit message quality, save time writing descriptive commits.

ai-plugins: Plugin Scaffolding#

Meta-plugin for creating new Claude Code plugins with interactive prompts, proper structure, and metadata.

Use case: Build custom plugins for your organization's specific workflows.

Each plugin solves a specific problem, but together they form a complete automation workflow that saves hours every week.

Why Open Source Matters#

I built these plugins to solve my own workflow problems - and I'm sharing them because other developers face the same challenges.

Benefits of Open Source#

• Transparency: Audit the code, understand exactly what commands do
• Customization: Fork and modify to match your organization's needs
• Community contributions: Improvements benefit everyone
• No vendor lock-in: Own your automation workflows
• Learning resource: See how Claude Code plugins are built

Fork and Customize#

Since the marketplace is distributed via GitHub, customization is straightforward:

# Fork the repository on GitHub
# Rename to avoid conflicts: yourcompany/claude-code-plugins-yourcompany

# Clone your fork
git clone https://github.com/yourcompany/claude-code-plugins-yourcompany
cd claude-code-plugins-yourcompany

# Customize plugin commands and templates
nano plugins/ai-ado/commands/ado-log-story-work.md

# Add your forked marketplace to Claude Code
/plugin marketplace add yourcompany/claude-code-plugins-yourcompany

# Install your customized plugins
/plugin install ai-ado@yourcompany/claude-code-plugins-yourcompany

Teams can create organization-specific workflows, naming conventions, and automation rules while benefiting from ongoing updates.

The Future of Developer Productivity#

Azure DevOps work item management doesn't have to be painful. The ai-ado plugin transforms what was once a 5-10 minute manual process into a 30-second automated workflow - without sacrificing quality or detail.

By leveraging AI-powered content generation, git commit detection, and Microsoft Azure DevOps MCP integration, the plugin ensures that no development detail gets lost. Your standup reports are comprehensive. Your work items include commit traceability. Your hour tracking is accurate. And you stay in flow - no context switching to web browsers or manual data entry.

But this is just one piece of the productivity puzzle. The open-source plugin marketplace includes tools for security auditing, performance optimization, git automation, and plugin development. Together, they form a comprehensive toolkit that saves hours every week and improves the quality of your work.

Whether you're logging work for daily standups, creating user stories for sprint planning, or managing complex feature hierarchies, ai-ado handles the automation so you can focus on what matters: writing great code.