chip-lint-resolver

Chip Lint Resolver

Resolves vc-spyglass lint violations by mapping each rule to its JMTAG execution level, then producing RTL modification proposals or waive files.

When to Use

• Processing vc-spyglass lint log output (.log, .rpt, .out)
• Need to map lint rule names to JMTAG execution standards
• Need to generate RTL fix proposals or waive files
• Debugging lint violations with wiki knowledge lookup

Core Workflow

0. Load blackbox module list
1. Parse lint log → extract (rule_name, file, line, message) tuples
2. Check blackbox → if module is BLACKBOX, auto-waive all its violations
3. Map remaining rules → JMTAG level via reference table
4. For each JMTAG level, execute the corresponding action
5. Output: RTL modification proposal + waive file

Step 0: Load Blackbox Module List

Read blackbox-modules.md (same directory as this SKILL.md) to load the blackbox module list.

A module is BLACKBOX if:

• Its module name matches an entry in the blackbox list, OR
• The violating file path contains a blackbox module name (e.g., ip/ahb_slave/ahb_slave.v matches blackbox entry ahb_slave)

Blackbox modules are typically:

• Third-party IP (not owned by the team)
• Pre-verified IP (already tape-out proven)
• Hard macros or analog wrappers
• Modules explicitly excluded from lint scope

If blackbox-modules.md is empty or missing, skip this step and process all violations normally.

Step 1: Parse Lint Log

vc-spyglass log format (typical patterns):

Warning [<rule_name>] <file>:<line> <message>
Error [<rule_name>] <file>:<line> <message>

Extract: rule_name, severity, file path, line number, violation message.

If log format is unknown, ask user to paste a sample or specify format.

Step 2: Filter Blackbox Violations

For each parsed violation, check if its module is in the blackbox list:

module_name ← extract from file path (e.g., "ahb_slave" from "ip/ahb_slave/ahb_slave.v")
if module_name in blackbox_list:
    → mark as BLACKBOX_WAIVED, skip JMTAG analysis