hoard-verify

Run lint, tests, and qmllint checks across hoard sub-packages.

Updated Mar 31, 2026

Search Tags:#typescript #go #verify #lint #tests #qml #hoard

Ready to run

npx skills add https://github.com/dotBeeps/pantry --skill hoard-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hoard-verify
Source: https://github.com/dotBeeps/pantry/tree/main/.claude/skills/hoard-verify
Command: npx skills add https://github.com/dotBeeps/pantry --skill hoard-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run a unified verification pass across hoard sub-packages to catch regressions early and stop on first critical failure with a clear report.

Core Features & Use Cases

Storybook-daemon (Go): lint with golangci-lint and run go test across all packages.
psi (Qt/QML): run qmllint on modified QML files.
berrygems (TypeScript): run tsc for changed TypeScript sources.
Output: provide a concise, per-sub-package report highlighting the first critical failure.

Quick Start

Run hoard-verify to perform the full verification pass across all sub-packages.

Frequently Asked Questions about hoard-verify

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

FAQPage Schema

How do I run lint and tests across Go, QML, and TypeScript components together?▼

You can run a unified verification pass across Go, QML, and TypeScript components to catch regressions early. It sequences golangci-lint, go test, qmllint, and tsc checks, stopping on the first critical failure and providing a clear report.

What is the best way to verify hoard sub-packages for build readiness?▼

Verifying hoard sub-packages for build readiness involves running lint, tests, and qmllint checks in sequence. This full verification pass scans Go, Qt/QML, and TypeScript sources, stopping immediately when a critical failure is detected.

Do I need golangci-lint and qmllint installed to verify mixed-language projects?▼

Yes, verifying mixed-language projects requires golangci-lint, go test, qmllint, and TypeScript tooling to be installed. These dependencies are necessary to scan code and accurately verify build and test readiness across all sub-packages.

How does the verification process handle errors in modified QML and TypeScript files?▼

The verification process handles errors by applying qmllint to modified QML files and tsc to changed TypeScript sources. If a critical failure is found during the sequence, the process stops and outputs a concise per-sub-package report.

Can I run lint and tests for Go packages alongside Qt/QML checks?▼

Yes, you can run lint and tests for Go packages alongside Qt/QML checks. The tool applies golangci-lint and go test to Go components and qmllint to Qt/QML components within a single sequential verification pass.

Why does the verification stop after the first critical failure?▼

The verification stops after the first critical failure to provide a clear, concise report highlighting the specific issue. This sequential execution model prevents cascading errors and helps developers quickly identify and fix the root cause of regressions.