check

Name: check
Availability: InStock
Author: kage1020

Run tests, linting, and builds to verify code quality.

Updated Mar 15, 2026

Search Tags:#automation #build #code-quality #lint #ci #tests #check

Ready to run

npx skills add https://github.com/kage1020/dotfiles --skill check-kage1020

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check
Source: https://github.com/kage1020/dotfiles/tree/main/dot_codex/skills/check
Command: npx skills add https://github.com/kage1020/dotfiles --skill check-kage1020

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates verification tasks to ensure code quality by running tests, linting, and builds.

Core Features & Use Cases

Run tests to confirm correctness of code changes.
Lint code to enforce style and quality standards.
Build or package the project to catch integration issues.
Use Case: Integrate into CI pipelines to gate merges based on passing tests and lint.

Quick Start

Run the check workflow to validate your codebase.

Frequently Asked Questions about check

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

FAQPage Schema

How do I automate code quality checks for tests, linting, and builds?▼

Automate code quality checks by running tests, linting, and builds sequentially to validate code health. This workflow confirms code correctness, enforces style standards, and catches integration issues before changes are merged into a project.

How do I integrate code verification into a CI pipeline to gate merges?▼

Integrate code verification into CI pipelines by running the automated check workflow to gate merges. Merges are blocked unless all testing, linting, and build steps pass, ensuring only validated code changes reach the main branch.

Do I need specific testing frameworks and a linter to run automated code checks?▼

Yes, running automated code checks requires existing testing frameworks, a linter, and a build step to execute. The workflow automates these tools sequentially and can be extended with project-specific configurations to match your environment.

What is the best way to validate codebase correctness before merging changes?▼

The best way to validate codebase correctness is running an automated workflow that executes tests, lint, and builds together. This comprehensive approach verifies code changes, enforces quality standards, and catches integration issues early.

Can I extend the code quality workflow with project-specific configurations?▼

Yes, you can extend the code quality workflow with project-specific configurations. This allows the automated tests, linting, and build steps to be tailored to the specific requirements and standards of your software project.