closeout-validate

Validate touched files with lint, test, smoke, and typecheck checks.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/h-4vok/diagram-tours --skill closeout-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: closeout-validate
Source: https://github.com/h-4vok/diagram-tours/tree/main/.agents/skills/closeout-validate
Command: npx skills add https://github.com/h-4vok/diagram-tours --skill closeout-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Closeout-validate helps teams prove that touched files were properly validated before closing a task, reducing late defects and audit questions by producing an explicit, reviewable checklist of validations.

Core Features & Use Cases

  • Inspect touched files and select only the checks that apply to those files and behavior:
    • modified JS/TS/Svelte/CSS files: lint
    • affected Vitest files: test
    • touched smoke specs or runtime-visible UI/CLI paths: smoke
    • affected package only: typecheck
  • Generate a closeout report listing inspected files and every command run, with a pass/fail status and justification.
  • Use for normal changes in codebases to demonstrate due diligence during change closures.

Quick Start

Run the closeout-validate workflow on your current task to generate a complete closeout report.

Frequently Asked Questions about closeout-validate

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

FAQPage Schema
How do I validate touched files before closing a software development task?

Linting modified JS, TS, Svelte, and CSS files before closing a task requires running a linter to catch syntax and style errors. The closeout validation process specifically targets these file types to ensure code quality standards are met before generating the final report.

How do I run Vitest tests for affected files during task closeout?

Validating package-only changes involves running typechecks to ensure type safety across the modified package. The closeout validation process detects package-only modifications and automatically executes the appropriate typecheck commands to produce validation evidence for the closeout report.

Can I generate a closeout report with pass and fail statuses for modified files?

Smoke checks are required for task closeout when touched files include smoke specs or runtime-visible UI and CLI paths. The validation process detects these runtime paths and executes targeted smoke checks to verify functional behavior before generating the final closeout report.

What is the best way to prove code changes are validated end-to-end?

The best way to prove code changes are validated end-to-end is to run a closeout validation workflow that inspects touched files and executes applicable checks. It compiles a concise report listing inspected files, commands run, and pass or fail justifications as reviewable evidence.