ticky

Name: ticky
Availability: InStock
Author: msifoss

Manage Azure DevOps work item lifecycles with YAML frontmatter tickets.

2|Updated Feb 17, 2026

Search Tags:#automation #devops #azure-devops #work-item #ticket-management #ticky

Ready to run

npx skills add https://github.com/msifoss/ai-dlc --skill ticky

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ticky
Source: https://github.com/msifoss/ai-dlc/tree/main/skills/skills/ticky
Command: npx skills add https://github.com/msifoss/ai-dlc --skill ticky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ticky streamlines the full lifecycle of Azure DevOps work items, from drafting locally to submitting to ADO, and ensures cross-repo visibility with consistent frontmatter-based tickets.

Core Features & Use Cases

Draft, submit, sync, and clean Azure DevOps work items across repositories with a single CLI.
Bidirectional sync with ADO, robust state tracking, and centralized ticket metadata in Markdown frontmatter.
Use case: A software team drafts a ticket in one repo, submits to ADO, then confirms status across multiple repos stays aligned.

Quick Start

Draft a sample ticket description to generate a local draft ticket with frontmatter for review.

Frequently Asked Questions about ticky

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage Azure DevOps work items from a local CLI?▼

You can manage Azure DevOps work items locally by drafting tickets in Markdown with YAML frontmatter, then using CLI modes like draft, submit, update, and clean to automate the full lifecycle directly from your repository.

How does cross-repo synchronization work for Azure DevOps tickets?▼

Cross-repo synchronization for Azure DevOps tickets works by maintaining a per-repo tickets.json catalog and bidirectionally syncing work item statuses, ensuring consistent state tracking across multiple repositories.

Do I need a personal access token to automate Azure DevOps ticket management?▼

Yes, you need a personal access token to authenticate and automate Azure DevOps ticket management, as the token provides the necessary access for submitting and syncing local work item drafts with your ADO project.

What is the best way to draft Azure DevOps tickets locally before submission?▼

The best way to draft Azure DevOps tickets locally is using a YAML frontmatter-driven Markdown format, which allows you to define ticket metadata and descriptions for review before submitting them to Azure DevOps.

Can I clean up outdated Azure DevOps work items across multiple repositories?▼

Yes, you can clean up outdated Azure DevOps work items across repositories using the clean mode, which identifies and removes outdated tickets while maintaining accurate metadata in your local tickets.json catalog.

Why use Markdown frontmatter for Azure DevOps work item tracking?▼

Markdown frontmatter provides centralized ticket metadata for Azure DevOps work item tracking, enabling robust state management and seamless bidirectional sync between local drafts and remote ADO environments.