claude-tweaks:test

Run type checks, lint, and tests from CLAUDE.md commands.

2|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/thomasholknielsen/claude-tweaks --skill claude-tweaks-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-tweaks:test
Source: https://github.com/thomasholknielsen/claude-tweaks/tree/main/skills/test
Command: npx skills add https://github.com/thomasholknielsen/claude-tweaks --skill claude-tweaks-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a mechanical verification gate that runs type checks, lint, and tests to confirm code changes are sound before they reach review or deployment.

Core Features & Use Cases

  • Automated type checking, linting, and test execution as a gating step within Claude Code workflows.
  • Integration with CLAUDE.md commands to discover project-specific verification procedures and orchestrate checks in the correct order.
  • Standardized results reporting and guidance for next actions, including QA story validation when stories exist.

Quick Start

Run /claude-tweaks:test to execute the verification gate and validate changes across types, lint, tests, and QA stories.

Frequently Asked Questions about claude-tweaks:test

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

FAQPage Schema
How do I automate type checks, lint, and tests before code review?

Automate type checks, lint, and tests by running a verification gate that orchestrates checks in order and reports results in a standard format. This Skill parses project commands from CLAUDE.md to execute mechanical gating steps before review or deployment.

What is a mechanical verification gate in a CI-like workflow?

A mechanical verification gate is an automated step that runs type checking, linting, and test execution to confirm code changes are sound. It orchestrates checks in the correct order by parsing project-specific procedures from CLAUDE.md, providing standardized results and next-action guidance.

How do I validate QA stories in YAML format during automated testing?

Validate QA stories in YAML format by running the verification gate, which includes QA story validation when stories exist within your workflow. The gate orchestrates checks in order and reports results in a standard format to confirm code changes are sound before review.

Can I use CLAUDE.md commands to discover project-specific verification procedures?

Yes, you can use CLAUDE.md commands to discover project-specific verification procedures. The Skill integrates with CLAUDE.md to parse custom commands, orchestrating type checks, lint, and tests in the correct order to ensure code changes meet mechanical gating requirements before review.

Does this verification gate work for CI-like pipelines and Claude Code workflows?

Yes, this verification gate works for CI-like pipelines and Claude Code workflows that require mechanical gates before review. It automates type checking, linting, and test execution, orchestrating checks in order and reporting standardized results to validate code changes and QA stories.

What are the limitations of automated verification gates for code changes?

Automated verification gates provide mechanical validation through type checks, lint, and tests, but they do not replace human review. They confirm code changes are sound before review or deployment by orchestrating checks in order, yet they are limited to the procedures defined in your CLAUDE.md commands.