triage

Convert legacy markdown todos into actionable entries with YAML frontmatter updates.

12|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jikig-ai/soleur --skill triage-jikig-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/jikig-ai/soleur/tree/main/plugins/soleur/skills/triage
Command: npx skills add https://github.com/jikig-ai/soleur --skill triage-jikig-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The triage skill helps convert legacy local todo markdown files into tracked, actionable work items by reviewing each finding and deciding whether to approve (ready), skip (delete), or customize before creating a todo entry.

Core Features & Use Cases

  • Structured Triage Workflow: Presents each finding with a consistent template including severity, category, location, proposed solution, and estimated effort.
  • File and Frontmatter Management: Renames pending files to ready, updates YAML frontmatter status and metadata, creates new todo files when needed, and deletes irrelevant items.
  • Use Cases: Processing legacy todos that predate GitHub issue integration, triaging code review findings, security audit results, and performance analysis items.

Quick Start

Run the triage skill to review todos in the todos/ directory and choose yes to approve, next to delete, or custom to modify each item.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I convert legacy todo markdown files into actionable tasks?

You can triage legacy todo markdown files by reviewing each item and choosing to approve, skip, or modify it. The process updates YAML frontmatter from pending to ready, renames files accordingly, and deletes skipped items.

Can I use this triage workflow to process code review findings and security audit results?

Yes, the triage workflow processes findings from code reviews, security audits, and performance analyses. It presents each finding with severity, category, location, proposed solution, and estimated effort before converting it into an actionable todo entry.

What is the best way to update YAML frontmatter status from pending to ready in local todos?

A structured triage process updates YAML frontmatter status from pending to ready while reviewing each todo item. It also manages file renames, creates new todo files, and deletes irrelevant items to maintain a clean task list.

Does the triage process modify code or is it strictly a review-only workflow?

The triage process enforces a review-only non-coding workflow. It exclusively manages markdown todo files through file renames, YAML frontmatter updates, new todo file creation, and deletion of skipped items.

How do I manage todos stored in the todos directory before integrating them with GitHub issues?

Run a triage workflow to manage todos in the todos directory by reviewing each pending markdown file and converting it into a ready task. This processes legacy todos predating GitHub issue integration using a consistent template.

What happens to skipped items during the todo markdown triage process?

During the todo markdown triage process, skipped items are permanently deleted. Choosing to skip a finding during review removes the irrelevant todo file, keeping the todos directory clean and focused on actionable work.