gf-lint

Lint SystemVerilog code with Verilator and produce categorized warnings and errors.

101|13|Updated Jan 28, 2026

Search Tags:#linting #verification #static-analysis #lint #CI #SystemVerilog #Verilator

Ready to run

npx skills add https://github.com/codejunkie99/Gateflow-Plugin --skill gf-lint

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gf-lint
Source: https://github.com/codejunkie99/Gateflow-Plugin/tree/main/plugins/gateflow/skills/gf-lint
Command: npx skills add https://github.com/codejunkie99/Gateflow-Plugin --skill gf-lint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SystemVerilog lint checker that identifies syntax and style issues in SV code, enabling teams to catch problems early and improve RTL quality.

Core Features & Use Cases

Verilator-based linting: Run lint checks across SV sources and categorize issues into errors and warnings.
Structured, parseable output: Returns a machine-friendly result block for orchestration and automation.
Use Case: Integrate into CI to enforce lint cleanliness before merges, or run locally to clean code iteratively.

Quick Start

Use the gf-lint skill to lint rtl/top.sv and print a structured summary.

Frequently Asked Questions about gf-lint

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

FAQPage Schema

How do I run SystemVerilog lint checks in CI to catch syntax and style issues?▼

SystemVerilog lint checks can be run in CI using Verilator to analyze SV files and produce structured warnings and errors for merge enforcement. The skill accepts explicit file lists or auto-detects SV files, returning a machine-friendly result block for orchestration.

What is the best way to lint SystemVerilog code locally before committing?▼

Linting SystemVerilog code locally is best done using Verilator to identify syntax and style issues iteratively. You can run the skill on specific SV files or auto-detected sources to get categorized warnings and errors for human review before committing changes.

Does Verilator support structured output for automated SystemVerilog linting?▼

Verilator supports automated SystemVerilog linting by parsing lint output into a structured, machine-friendly result block. This enables orchestration and automation, allowing teams to categorize issues into errors and warnings for CI or human review.

How do I parse Verilator lint warnings across multiple SystemVerilog files?▼

Verilator lint warnings across multiple SystemVerilog files can be parsed by running the skill with explicit file lists or auto-detected SV sources. It categorizes the lint output into structured warnings and errors for orchestration and CI integration.

Do I need Verilator installed to lint SystemVerilog code for CI pipelines?▼

You need Verilator installed and the ability to parse lint output to lint SystemVerilog code for CI pipelines. The skill requires Verilator to run lint checks on SV files and produce categorized warnings and errors in a structured result block.

Can I auto-detect SystemVerilog files for Verilator lint runs?▼

Auto-detecting SystemVerilog files for Verilator lint runs is supported by the skill, which accepts explicit file lists or automatically finds SV files across projects. It then returns a structured result block with categorized warnings and errors for CI or human review.