skills.rest
Space-Dinosaurs
Space-DinosaursOFFICIAL
Explore all skills by this author →
Website𝕏@SpaceDinosaurS6GitHub

ticket-status-sync

Reconcile ticket tracker columns with actual code state.

12|1|Updated Apr 7, 2026
Search Tags:#automation#github#status#ticket#reconciliation#tracker
One-click install
npx skills add https://github.com/Space-Dinosaurs/DinoStack --skill ticket-status-sync-space-dinosaurs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-status-sync
Source: https://github.com/Space-Dinosaurs/DinoStack/tree/main/.openclaw/skills/ticket-status-sync
Command: npx skills add https://github.com/Space-Dinosaurs/DinoStack --skill ticket-status-sync-space-dinosaurs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconciles a ticket's tracker column with the actual state of its code. This hands-off alignment prevents mis-states on tickets after code changes or merges.

Core Features & Use Cases

  • Reconcile a single ticket's tracker status with the code state to ensure accurate progress.
  • Bulk reconcile: sweep all non-terminal tickets in .agentic/tasks.jsonl to realign tracker states.
  • Forward-only transitions: only apply changes when the current tracker rank is lower than the computed target, preventing regressive updates.

Quick Start

Run /ticket-status-sync <TICKET_ID> to reconcile a ticket's tracker status with its code state, or run /ticket-status-sync --all to perform a bulk reconciliation across all non-terminal tickets in .agentic/tasks.jsonl.

Frequently Asked Questions about ticket-status-sync

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

FAQPage Schema
How do I sync ticket tracker status with actual code state after merging?▼

Ticket tracker status sync reconciles a ticket's tracker column with the actual state of its code, automatically aligning progress tracking after code changes or merges to prevent mis-states.

How do I bulk reconcile all non-terminal tickets in .agentic/tasks.jsonl?▼

Bulk ticket reconciliation sweeps all non-terminal tickets in .agentic/tasks.jsonl to realign tracker states with computed targets, using forward-only guarded transitions to prevent regressive updates.

Why does ticket reconciliation only apply forward-only transitions?▼

Forward-only ticket transitions prevent regressive updates by applying changes only when the current tracker rank is lower than the computed target, ensuring tracker state never moves backward during code reconciliation.

Can I run ticket status sync for periodic bulk sweeps across active tasks?▼

Periodic ticket status reconciliation supports bulk sweeps across all non-terminal tickets in .agentic/tasks.jsonl, applying soft-fail behavior to safely realign tracker columns without interrupting the workflow.

Does ticket status sync require a specific task file format or branch state?▼

Ticket reconciliation reads task, PR, and branch state from .agentic/tasks.jsonl entries, using the same resolution rules as the Tracker Writeback helper to compute target states from actual code conditions.

What happens when ticket status sync encounters an invalid state transition?▼

Soft-fail ticket reconciliation behavior skips invalid state transitions instead of failing, continuing the bulk sweep across remaining non-terminal tickets while applying only valid forward-only guarded transitions.

Related Skills

Explore More Software Engineering Skills→
LarryHsiaoLarryHsiao

celebrimbor

Automate approved counsel into code changes and a forge PR/MR workflow.

Community
Advanced
ZzAveZzAve

prototype

Execute terminal-based state model prototypes for manual state transitions.

Community
Advanced
J03Fr0stJ03Fr0st

to-tickets

Convert project plans and specifications into structured issue tracker tickets.

Community
Intermediate
darylmcddarylmcd

reconcile-backlog-sweep-plan

Reconcile backlog-sweep plan state.json and plan.md against GitHub PR statuses.

Community
Advanced