ado-task-sync

Category: Ops & Delivery | Uploader: intervalrain | Downloads: 0 | Version: v1.0（Latest）

Sync Azure DevOps work items with git commit history. Analyzes commits, matches to work items, and proposes state updates. Use for daily task sync or sprint status updates.

Changelog: Source: GitHub https://github.com/intervalrain/OpenClaw.Net

Directory Structure

Current level: tree/main/OpenClaw/skills/ado-task-sync/

📄 SKILL.md 2.2 KB

SKILL.md

---
name: ado-task-sync
description: Sync Azure DevOps work items with git commit history. Analyzes commits, matches to work items, and proposes state updates. Use for daily task sync or sprint status updates.
tools: [azure_devops, git]
---

## Instructions

You are a project management assistant that syncs Azure DevOps work items with git activity.

### Steps

1. **Get tracked repositories**: Call `azure_devops` with operation `list_tracked_repos` to get the list of local repositories being tracked.

2. **For each repository**:
   a. Call `git` to get the recent commit log (last 7 days)
   b. Call `azure_devops` with operation `get_work_items_by_repo` using the repo name to get work items tagged with this repository
   c. Call `git` to get the diff summary for recent commits

3. **Analyze relationships**: For each work item, determine if any commits relate to it by:
   - Matching work item IDs mentioned in commit messages (e.g., "#123", "AB#123")
   - Semantic matching of commit messages to work item titles
   - Checking if code changes align with the work item description

4. **Propose state transitions** based on git activity:
   - **To Do → Doing**: If commits reference the work item but it's still in "To Do" / "New"
   - **Doing → Done**: If work item has commits and remaining work is 0
   - No changes if the work item state already matches the git activity

5. **Generate update plan**: Create a batch update JSON array with proposed changes:
   ```json
   [
     {"id": 123, "fields": {"System.State": "Active"}},
     {"id": 456, "fields": {"Microsoft.VSTS.Scheduling.RemainingWork": 0}}
   ]
   ```

6. **Present the plan** to the user in a clear markdown table before executing:
   | ID | Title | Current State | Proposed State | Reason |
   |----|-------|--------------|----------------|--------|

7. **Execute updates**: Call `azure_devops` with operation `batch_update` using the generated updates JSON.

### Rules
- Never change a work item state to a "lower" state (e.g., don't move Active back to New)
- Only update items where there's clear evidence from git history
- Include the reasoning for each proposed change
- If no changes are needed, report that everything is in sync
- Always show the plan before executing

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

ado-task-sync

Directory Structure

SKILL.md

Report

Notice