triage

Converts Claude Code /insights outputs into GitHub issues across repos.

24|1|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/rmzi/portable-dev-system --skill triage-rmzi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/rmzi/portable-dev-system/tree/main/skills/triage
Command: npx skills add https://github.com/rmzi/portable-dev-system --skill triage-rmzi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage insights into actionable GitHub issues across repos. Use after running /insights to convert analysis into tracked work.

Core Features & Use Cases

  • Reads Claude Code /insights output (report.html, facets, session-meta) and maps findings to repositories.
  • Performs per-section interactive triage with deduplication against prior runs.
  • Persists a snapshot and manifest to enable later triage and prevent duplicates.

Quick Start

Run /pds:triage to begin interactive triage of your latest insights.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I turn Claude Code insights into GitHub issues?

To turn Claude Code insights into GitHub issues, run the triage skill after generating /insights. It reads report.html and session-meta data, groups friction and feature items, and creates tracked issues across multiple repos with interactive confirmation.

What is the best way to triage Claude Code analysis outputs across multiple repositories?

Triage of Claude Code analysis outputs across multiple repositories is handled by reading report.html and facets, mapping findings to target repos, and performing per-section interactive confirmation before issue creation to ensure accurate tracking.

How does deduplication work when converting session insights into tracked issues?

Deduplication when converting session insights into tracked issues works by comparing new findings against prior persisted manifests. The skill saves a snapshot of previous triage runs to prevent duplicate GitHub issues from being created in future sessions.

Can I interactively confirm GitHub issue creation from Claude Code friction reports?

Yes, you can interactively confirm GitHub issue creation from Claude Code friction reports. The skill performs per-section triage, allowing you to review grouped friction, feature, and horizon items before any issue is actually created.

Do I need to run /insights before triaging Claude Code session data into GitHub issues?

Yes, you need to run /insights before triaging Claude Code session data into GitHub issues. The skill specifically reads the generated report.html, facets, and session-meta data to map findings and deduplicate against prior runs.