halt-review

Review Go, Templ, and Lit projects for HALT architecture consistency.

Updated May 3, 2026
One-click install
npx skills add https://github.com/ousiass/dotfiles --skill halt-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: halt-review
Source: https://github.com/ousiass/dotfiles/tree/main/.claude/skills/halt-review
Command: npx skills add https://github.com/ousiass/dotfiles --skill halt-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

HALT architecture projects can drift over time as routes, Templ/HTMX bindings, Atomic Design boundaries, and Lit Web Component conventions evolve, leading to broken UX, runtime errors, or security regressions.

Core Features & Use Cases

  • HALT Phase-based architecture review: Automatically inspects project structure first, then runs targeted checks across routing, Templ↔HTMX, cross-layer bindings, HATEOAS rules, Atomic Design layering, Lit conventions, Go layered architecture, security, and build configuration.
  • Actionable, evidence-based findings: Reports only verifiable issues with file paths and line numbers, assigns severity (Critical/Important/Suggestion/Minor), and suggests concrete fixes.
  • Report output routing: Produces a consolidated review report via GitHub Issue (recommended), a local Markdown file, or direct console output using a shared template.

Quick Start

Run halt-review to review the current project directory and generate a HALT architecture report.

Frequently Asked Questions about halt-review

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

FAQPage Schema
How do I validate HALT architecture consistency across Go, Templ, and Lit components?

To validate HALT architecture consistency, run an automated review that checks routing, Templ↔HTMX integration, cross-layer contracts, and Lit conventions against your Go backend. It verifies file evidence for mismatched API routes and attribute bindings.

What is HALT architecture review and when do I need it?

HALT architecture review is a deterministic inspection of project structure, routing, HATEOAS rules, and Atomic Design layering. You need it when your Go, Templ, and Lit project drifts, causing broken UX, runtime errors, or security regressions during development.

How do I check Templ and HTMX integration for mismatched routes and attribute bindings?

To check Templ and HTMX integration for mismatched routes, perform a file-evidence-based review that inspects API routes and attribute bindings across your project layers. It identifies mismatches with specific file paths and line numbers.

Can I use this architecture review tool with Go backends using Lit Web Components and Atomic Design?

Yes, this architecture review tool is explicitly designed for projects using Go backends with Templ templates and Lit Web Components where Atomic Design layering and HATEOAS conventions must remain correct during development.

How do I enforce CSRF protection and authorization in a HALT architecture project?

To enforce CSRF protection and authorization in a HALT architecture project, run a security-focused architecture review that performs deterministic checks for authorization and CSRF enforcement. It reports security-critical behavior regressions with evidence.

What is the best way to report architecture drift and layer dependency violations in a Go project?

The best way to report architecture drift and layer dependency violations is to generate a consolidated review report via GitHub Issue, local Markdown file, or console output. It assigns severity levels and suggests concrete fixes based on file evidence.