vida-github-issues

Triage GitHub Issues and map them to TaskFlow tasks with operator approval.

16|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/pomazanbohdan/vida-stack --skill vida-github-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vida-github-issues
Source: https://github.com/pomazanbohdan/vida-stack/tree/main/.agents/skills/vida-github-issues
Command: npx skills add https://github.com/pomazanbohdan/vida-stack --skill vida-github-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

GitHub issues often become noisy and misaligned with project execution. This Skill triages issues and maps them to TaskFlow tasks, ensuring proper ownership, traceability, and timely resolution.

Core Features & Use Cases

  • Triage: Identify open issues relevant to VIDA Stack projects and extract actionable work items.
  • Mapping to TaskFlow: Link issues to corresponding Tasks/Epics and reflect proof state in TaskFlow.
  • Guardrails: Enforce untrusted data handling, require operator approval for mutations, and prevent premature closures.

Quick Start

Map the highest-priority open GitHub issue in the VIDA Stack repository to a new or existing TaskFlow epic with traceable evidence.

Frequently Asked Questions about vida-github-issues

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

FAQPage Schema
How do I triage GitHub issues and map them to project execution tasks?

Triaging GitHub issues involves extracting actionable work items from open repository issues and mapping them to TaskFlow tasks, ensuring proper ownership, traceability, and timely resolution.

What is the best way to clean up stale GitHub issues in a repository?

Stale issue cleanup is handled by triaging open issues to identify misaligned or outdated items, then mapping relevant items to TaskFlow tasks to drive accountability before requiring explicit operator approval.

Can I map a GitHub issue to an existing epic without manual data entry?

Yes, you can map the highest-priority open GitHub issue to a new or existing TaskFlow epic, automatically linking the issue to corresponding tasks while reflecting proof state with traceable evidence.

Does this GitHub issue triage workflow require approval before making changes?

Yes, the GitHub issue triage workflow requires explicit operator approval before any mutations occur, enforcing untrusted data handling and preventing premature issue closures.

How does issue-to-epic synchronization handle runtime diagnostics?

Issue-to-epic synchronization focuses on open repositories to process runtime diagnostics, mapping issues to TaskFlow tasks with traceable evidence to drive accountability and track progress accurately.

Are there limitations when mapping untrusted GitHub issue data to TaskFlow?

The workflow enforces untrusted data handling for GitHub issues by requiring traceable evidence for mappings and preventing premature closures, meaning no mutations happen without explicit operator approval.