debug
Find why an FPGA build failed (Vivado, HLS, PetaLinux) and how to fix it.
Install
npx skills add https://github.com/al-nafisah/fpga-project-analyzer/tree/main/skills/debug
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install al-nafisah-fpga-project-analyzer@llmmart
git clone https://github.com/al-nafisah/fpga-project-analyzer.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole al-nafisah/fpga-project-analyzer collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Find why the FPGA build failed. Arguments ($ARGUMENTS) are a log file or a project folder; if none, use the current
folder and the logs with errors that the build summary lists first.
Read ../fpga-project-analyzer/SKILL.md (relative to this file's directory) and follow it: logs for the log,
build + show to locate the cause in the design. Reply with the root cause, where it is (file:line or block),
and the exact fix.
Files (fpga-project-analyzer)
-
SKILL.md 612 B
--- name: debug description: Find why an FPGA build failed (Vivado, HLS, PetaLinux) and how to fix it. argument-hint: "[log file or project folder]" disable-model-invocation: true --- Find why the FPGA build failed. Arguments ($ARGUMENTS) are a log file or a project folder; if none, use the current folder and the logs with errors that the build summary lists first. Read `../fpga-project-analyzer/SKILL.md` (relative to this file's directory) and follow it: `logs` for the log, `build` + `show` to locate the cause in the design. Reply with the root cause, where it is (file:line or block), and the exact fix.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.