fls-issue-triage

Triage FLS issues and implement spec updates from linked Rust changes.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/PLeVasseur/opencode-project-agents --skill fls-issue-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fls-issue-triage
Source: https://github.com/PLeVasseur/opencode-project-agents/tree/main/fls/skills/fls-issue-triage
Command: npx skills add https://github.com/PLeVasseur/opencode-project-agents --skill fls-issue-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage FLS issues and implement spec updates from linked Rust changes.

Core Features & Use Cases

  • Determine whether changes impact FLS semantics, syntax, or glossary.
  • Map updates to src/*.rst sections and update references, changelogs, and glossary terms.
  • Ensure alignment with the Rust 2021 edition and document any backport considerations.

Quick Start

Start by assessing the issue, determining FLS impact, and initiating the update workflow.

Frequently Asked Questions about fls-issue-triage

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

FAQPage Schema
How do I triage FLS issues linked to Rust changes?

Triage FLS issues by assessing linked Rust changes to determine their impact on FLS semantics, syntax, or glossary. It then maps these updates to src/*.rst sections and generates a report with provenance and sources.

What is the best way to map Rust spec updates to FLS sections?

Map Rust spec updates by identifying new glossary terms and applying changes to relevant src/*.rst sections. This ensures alignment with the Rust 2021 edition while updating references and changelogs.

Does this triage process handle Rust 2021 edition alignment?

Yes, the triage process explicitly ensures alignment with the Rust 2021 edition. It documents any backport considerations when applying spec updates from linked Rust changes to FLS.

How do I update FLS glossary terms from Rust changes?

Update FLS glossary terms by identifying new terms introduced in linked Rust changes. The workflow maps these terms to relevant sections and updates the glossary alongside references and changelogs.

When do I need to document backport considerations for FLS updates?

Document backport considerations during FLS updates when linked Rust changes impact language semantics or syntax within the Rust 2021 edition context. The triage report includes provenance and sources for these considerations.

Can I generate a provenance report for FLS spec updates?

Yes, the triage workflow generates a report with provenance and sources after applying spec updates. This report documents how linked Rust changes impact FLS semantics, syntax, and glossary sections.