fls-audit

Run the FLS audit tool and summarize changes from build/fls_audit/report.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run the FLS audit tool and summarize changes, helping teams track guideline updates without reimplementing diff logic.

Core Features & Use Cases

  • Run the FLS audit tool to generate a concise report from build/fls_audit/report.md.
  • Compare before/after diffs, identify added/removed/changed guidelines, and highlight affected guidelines.
  • Provide a structured summary including counts, affected areas, and top-3 heuristic matches per paragraph.

Quick Start

Run the FLS audit tool and review the generated report to capture guideline changes.

Frequently Asked Questions about fls-audit

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

FAQPage Schema
How do I automate an FLS spec lock audit to track guideline updates?▼

To automate an FLS spec lock audit, the Skill invokes the audit tool and reads the generated build/fls_audit/report.md file to summarize guideline changes across software project releases.

What is an FLS audit report and how does it summarize compliance changes?▼

An FLS audit report is a structured summary generated from build/fls_audit/report.md that provides counts of added, removed, and changed guidelines, along with top paragraph matches for compliance tracking.

How do I compare before and after diffs for software project guidelines?▼

Comparing before and after diffs for software guidelines involves running the FLS audit tool to identify affected areas, highlight changed guidelines, and present heuristic matches per paragraph.

Can I use this audit tool to assess the impact of guideline updates across releases?▼

Yes, the audit tool assesses the impact of guideline updates across releases by generating a concise report with counts of changes, affected areas, and the top-3 heuristic matches per paragraph.

What is the best way to summarize FLS audit results without reimplementing diff logic?▼

The best way to summarize FLS audit results without reimplementing diff logic is to invoke the audit tool and parse the existing build/fls_audit/report.md for structured counts and impact summaries.

Do I need a specific build directory structure to run an FLS audit?▼

Yes, you need a build directory containing the fls_audit/report.md file, which the audit tool generates and the Skill reads to present concise summaries of guideline changes and impacts.