sync-tasks

Synchronize planning docs and GitHub issues across multiple repositories.

8|1|Updated Dec 9, 2024
One-click install
npx skills add https://github.com/dianlight/srat --skill sync-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-tasks
Source: https://github.com/dianlight/srat/tree/main/.github/skills/sync-tasks
Command: npx skills add https://github.com/dianlight/srat --skill sync-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps planning documents in docs/tasks aligned with GitHub issues and in-code TODO/FIXME annotations by synchronizing across sources and repositories. It coordinates three modes—IMPORT, EXPORT, and CODE-SCAN—to pull issues, push progress, and annotate code references into task planning, ensuring a single source of truth for work items.

Core Features & Use Cases

  • Import issues from GitHub into docs/tasks and create or update tasks based on issue data.
  • Push task progress to linked GitHub issues (comments, status updates, closure) and create missing issues when needed.
  • Scan code for TODO/FIXME marks and map them to existing tasks or generate new planning entries, with de-duplication and linking rules.
  • CODE-SCAN mode enriches tasks with code references and ensures traceability between code changes and planning artifacts.

Quick Start

Run the sync-tasks skill to import issues, scan code comments, and export progress to GitHub.

Frequently Asked Questions about sync-tasks

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

FAQPage Schema
How do I sync planning docs with GitHub issues across multiple repos?

To sync planning docs with GitHub issues, use a three-mode synchronization approach covering IMPORT, EXPORT, and CODE-SCAN. This pulls open issues into your task plans, pushes task progress back as GitHub comments or status updates, and scans code annotations to maintain alignment across repositories.

What is the best way to track TODO and FIXME tags in code as GitHub tasks?

Tracking TODO and FIXME tags involves scanning your codebase for these annotations and mapping them to existing planning docs or generating new task entries. The CODE-SCAN mode handles this by enriching tasks with code references and applying de-duplication rules to ensure traceability between code changes and planning artifacts.

Can I export task progress from my planning documents to update linked GitHub issues?

Yes, exporting task progress to linked GitHub issues is supported through the EXPORT mode. It pushes progress updates, status changes, and closures to GitHub, and automatically creates missing issues when needed based on your planning document data.

How does de-duplication work when importing GitHub issues into task planning docs?

De-duplication when importing GitHub issues prevents duplicate planning entries by applying specific task creation and linking rules. The IMPORT mode checks existing tasks before creating new ones, ensuring a single source of truth for work items across your planning documents.

When should I use CODE-SCAN mode for synchronizing planning docs and GitHub issues?

CODE-SCAN mode should be used when you need to ensure traceability between code changes and planning artifacts. It scans your code for TODO and FIXME marks, maps them to existing tasks, or generates new planning entries while gating when to push changes to avoid unnecessary updates.