check

Run linting, type-checking, formatting, and tests across project languages.

1|1|Updated Feb 28, 2024
One-click install
npx skills add https://github.com/jiyeol-lee/dotfiles --skill check-jiyeol-lee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/jiyeol-lee/dotfiles/tree/main/.opencode/skills/check
Command: npx skills add https://github.com/jiyeol-lee/dotfiles --skill check-jiyeol-lee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Verifies code quality through linting, type-checking, formatting, and testing. Use when asked to "run checks", "validate code", "lint this", "check for errors", "run tests", or "verify code quality" before or after changes.

Core Features & Use Cases

  • Runs linters and reports violations (does NOT auto-fix lint errors)
  • Runs type checkers and reports errors
  • Auto-fixes formatting only (prettier, black, go fmt, ruff format)
  • Runs tests (unit + integration)
  • Philosophy: Verify and report. Only auto-fix formatting. All other issues go to orchestrator.

Quick Start

Run lint, type-check, format (auto-fix only), and tests in the project, then report all findings to the orchestrator.

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 before commits?

Automate code quality checks by running linting, type-checking, formatting, and tests in a defined order. This detects project tooling, verifies code quality, and reports all findings with file paths and error messages before commits or during CI.

Can I auto-fix linting and type-checking errors during code validation?

Code validation does not auto-fix linting or type-checking errors. It only auto-fixes formatting using tools like prettier, black, go fmt, or ruff format, while verifying and reporting all other violations to the orchestrator.

What is the best way to run lint and tests across multiple languages in CI?

Run lint and tests across multiple languages by detecting project tooling automatically and executing checks in a defined order. This validates code quality during CI and reports all findings with specific file paths and error messages.

Does code verification work with projects using different formatting tools?

Code verification works with projects using various formatting tools by detecting project tooling automatically. It supports auto-fixing formatting only for tools like prettier, black, go fmt, and ruff format, while reporting lint and type errors.

Why does my formatting check auto-fix but linting errors only get reported?

Formatting checks auto-fix because the philosophy is to verify and report, only auto-fixing formatting. Linting and type-checking errors are intentionally not auto-fixed, ensuring all other issues are reported to the orchestrator for review.