ginee-triage

Aggregate GitHub issues and TODO files into a merged backlog table.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kostiantyn-matsebora/ginee --skill ginee-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ginee-triage
Source: https://github.com/kostiantyn-matsebora/ginee/tree/main/core/skills/ginee-triage
Command: npx skills add https://github.com/kostiantyn-matsebora/ginee --skill ginee-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill collects and presents a unified backlog view by aggregating ready work from GitHub issues and TODO files across sources. It proposes a deterministic pickup order and prevents automatic execution.

Core Features & Use Cases

  • Merged view: combines issues from primary repo and framework upstream with TODOs into a single table.
  • Scope-aware triage: supports global and scoped views (issues, framework, todos) to focus work.
  • Guardrails: surfaces proposed picks without taking action, leaving execution to a human.

Quick Start

Ask me to triage to generate a merged backlog view from issues and TODOs.

Frequently Asked Questions about ginee-triage

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

FAQPage Schema
How do I aggregate GitHub issues and TODO files into a single backlog view?

To triage issues and TODOs into a merged backlog, aggregate ready work from GitHub issues and TODO files using a local scoring formula. The skill parses scoring markers, computes scores, sorts items by score and age, and presents them as a single table.

How are GitHub issues scored and sorted in an automated backlog triage?

Automated backlog triage scores GitHub issues by parsing scoring markers from the text and computing a score using a local triage formula. The system then sorts all aggregated ready work by both score and age to propose a pickup order.

Can I automatically pick up and execute the top ranked task from my backlog?

No, you cannot automatically execute tasks because the triage skill includes guardrails that prevent automatic execution. It surfaces proposed picks with explicit pickup instructions, leaving the final execution decision to a human.

What is the best way to scope my backlog triage to focus only on framework upstream issues?

The best way to scope backlog triage to framework upstream issues is to use scope-aware triage features. This supports global and scoped views, allowing you to filter the merged table specifically for framework upstream issues, primary repo issues, or todos.

Does backlog triage work with both GitHub issues and local TODO files?

Yes, backlog triage works with both GitHub issues and local TODO files by combining them into a single merged table. It aggregates ready work across these multiple sources to provide a unified backlog view.