triage-display

Format triage results as terminal-ready markdown and parse review commands.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/jeremylongshore/x-bug-triage-plugin --skill triage-display
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-display
Source: https://github.com/jeremylongshore/x-bug-triage-plugin/tree/main/skills/triage-display
Command: npx skills add https://github.com/jeremylongshore/x-bug-triage-plugin --skill triage-display

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Formats triage results for terminal-ready markdown and provides reliable parsing of interactive review commands to drive the triage workflow.

Core Features & Use Cases

  • Formats triage results as terminal-ready markdown for quick review.
  • Parses and validates review commands (details, file, dismiss, merge) for deterministic routing.
  • Supports consistent rendering and integration with the triage-server pipeline in automated and manual workflows.

Quick Start

Render a terminal-ready triage summary by invoking the triage-display step in the triage workflow.

Frequently Asked Questions about triage-display

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

FAQPage Schema
How do I format triage results as terminal-ready markdown for quick review?

Terminal-ready markdown formatting renders triage results into structured text for quick terminal review. It parses review commands like details, file, dismiss, and merge to drive deterministic cluster actions during triage sessions.

What review commands can I use during a terminal triage session?

Interactive review commands include details, file, dismiss, and merge. The parser validates these commands to ensure deterministic routing and reliable execution of cluster actions within the triage workflow.

How does terminal triage display integrate with an automated workflow pipeline?

Terminal triage display integrates with the triage-server pipeline by providing consistent rendering and deterministic command parsing. This ensures both automated and manual workflows can reliably process triage clusters.

Do I need specific dependencies to render triage clusters in the terminal?

No external dependencies are required to render triage clusters in the terminal. The formatting operates independently using frontmatter-defined fields to generate terminal-ready markdown output.

What's the best way to parse interactive review commands for deterministic cluster actions?

Parsing interactive review commands deterministically requires validating inputs like details, file, dismiss, and merge. This ensures commands route reliably to the correct cluster actions without ambiguity during triage sessions.

Why does my terminal triage display need frontmatter-defined fields?

Frontmatter-defined fields satisfy structural requirements for deterministic rendering within the triage-server pipeline. They ensure triage results format consistently as terminal-ready markdown and that review commands parse correctly.