check

Automates Hugo site QA checks for builds, links, and assets in CI workflows.

2|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/MinBZK/moza-site --skill check-minbzk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/MinBZK/moza-site/tree/main/.claude/skills/check
Command: npx skills add https://github.com/MinBZK/moza-site --skill check-minbzk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates quality assurance checks on a Hugo site to verify a successful build and detect broken links, missing assets, and template issues that hinder publish readiness.

Core Features & Use Cases

  • Build verification: Run the Hugo build to confirm the site compiles without errors.
  • Link and asset checks: Identify broken internal or external links and missing assets.
  • Pre-commit and CI readiness: Use during local development or CI to catch issues before deployment.

Quick Start

Run just build to compile the site, then run just check to execute quality checks. Review any reported issues and decide whether to address content, accessibility, or SEO as needed.

Frequently Asked Questions about check

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

FAQPage Schema
How do I check a Hugo build for broken links and missing assets?

Hugo build verification runs automated quality checks to compile the site and identify broken internal or external links alongside missing assets. This process confirms templates and content render correctly before deployment.

What is the best way to automate Hugo pre-commit quality checks?

Automating Hugo pre-commit checks involves running build and lint validations locally to catch broken links and template issues early. This ensures your static site compiles correctly and is fully ready for continuous integration workflows.

Can I run Hugo link checks and content validation in CI workflows?

Yes, you can execute Hugo link checks within CI workflows to validate successful site builds and detect broken links. This identifies missing assets and template errors to ensure publish readiness before deployment.

Does Hugo build verification detect missing assets and template issues?

Yes, Hugo build verification detects missing assets and template issues by executing the build process and running follow-up validations. It reports these errors in clear, actionable language to help resolve content and accessibility problems.

Why do I need to run Hugo quality checks if my local build succeeds?

You need Hugo quality checks because a successful local build does not guarantee intact links or valid assets. Quality checks identify broken internal and external references to ensure content, accessibility, and SEO meet deployment standards.