lint-triage

Automates RTL linting and methodology violation triage via SynthOol tools.

11|7|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/LNC0831/oh-my-fpga --skill lint-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-triage
Source: https://github.com/LNC0831/oh-my-fpga/tree/main/skills/lint-triage
Command: npx skills add https://github.com/LNC0831/oh-my-fpga --skill lint-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of overwhelming, unorganized RTL linting warnings by providing a structured, methodology-driven approach to triage violations into actionable fixes, documented waivers, or human-review items.

Core Features & Use Cases

  • Methodology-Driven Triage: Systematically categorizes violations into fix, waive, or ask buckets based on FPGA design best practices.
  • Synthesis-Aware Analysis: Integrates with Vivado to perform deep checks like latch inference, FSM health, and CDC linting on synthesized netlists.
  • Use Case: Use this skill to clean up a complex design before synthesis sign-off by identifying unintended latches, width mismatches, and coding style violations that would otherwise cause hardware bugs.

Quick Start

Invoke the lint-triage skill to perform a full RTL quality review and generate a triage report for the current project.

Frequently Asked Questions about lint-triage

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

FAQPage Schema
How do I triage RTL linting warnings for FPGA synthesis sign-off?

RTL linting triage categorizes violations into actionable fixes, documented waivers, or human-review items using a structured methodology. This organizes overwhelming warnings before FPGA synthesis sign-off.

How do I detect unintended latches in synthesized Vivado netlists?

Detecting unintended latches in Vivado requires synthesis-aware analysis on the synthesized netlist. This methodology evaluates latch inference, FSM health, and clock domain crossing violations.

Do I need an active Vivado Tcl server to analyze FPGA methodology violations?

Yes, an active Vivado Tcl server connection and an open synthesized design are required to perform full methodology-stage analysis. This environment enables deep linting checks on the netlist.

What is the best way to classify FPGA coding style violations before hardware bugs occur?

The best way to classify FPGA coding style violations is a systematic triage that evaluates width mismatches and style issues against design best practices. This structures violations into fix, waive, or ask buckets.

Can I use methodology-driven lint triage without an open synthesized design?

No, full methodology-stage analysis requires an open synthesized design. An active Vivado Tcl server connection and synthesized netlist are necessary to execute deep checks like latch inference.