skills.rest
RafayelGardishyan
RafayelGardishyanCOMMUNITY
Explore all skills by this author →
GitHub

check

Run golangci-lint, Biome, and svelte-check quality checks before commits.

Updated Mar 9, 2026
Search Tags:#code-quality#ci-cd#quality-assurance#lint#typecheck#golangci-lint#frontend-lint
One-click install
npx skills add https://github.com/RafayelGardishyan/rafayels-marketplace --skill check-rafayelgardishyan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/RafayelGardishyan/rafayels-marketplace/tree/main/plugins/rafayels-engineering/.opencode/skills/check
Command: npx skills add https://github.com/RafayelGardishyan/rafayels-marketplace --skill check-rafayelgardishyan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often face quality regressions due to inconsistent linting and missing type checks across Go and frontend projects. This skill provides a unified, repeatable set of checks (Go lint, frontend lint, and typechecking) to catch issues before they reach code review.

Core Features & Use Cases

  • Go lint: golangci-lint with depguard architecture rules, errcheck, gosec, and complexity limits.
  • Frontend lint: Biome-based lint for frontend/ and modules/chat/frontend/.
  • Typecheck: svelte-check on frontend projects.
  • Use Case: Before committing or creating a PR, run the checks to ensure code quality is maintained and avoids review-blocking failures.

Quick Start

Run make check to execute all checks.

Frequently Asked Questions about check

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

FAQPage Schema
How do I run automated lint and type checks before creating a PR?▼

Automated lint and type checks before a PR are run via `make check`, which executes golangci-lint for Go, Biome for frontend linting, and svelte-check for typechecking to catch errors before code review.

What is the best way to enforce Go architecture rules and complexity limits in CI?▼

Enforcing Go architecture rules and complexity limits is done via golangci-lint configured with depguard, errcheck, gosec, and complexity limits, catching architectural violations and security issues before code review.

Can I use Biome and svelte-check together for frontend linting and typechecking?▼

Biome and svelte-check are used together to provide frontend linting and typechecking; Biome handles linting for frontend directories while svelte-check executes typechecking across multiple frontend projects.

Does this automated code quality check work with both Go and frontend projects?▼

This automated code quality check works with both Go and frontend projects, applying golangci-lint to Go code and utilizing Biome alongside svelte-check for frontend directories including modules/chat/frontend.

Why should I run quality checks before committing code instead of waiting for review?▼

Running quality checks before committing catches linting and type errors early, preventing review-blocking failures and avoiding quality regressions caused by inconsistent checks across Go and frontend projects.

Related Skills

Explore More Software Engineering Skills→
sizukutamagosizukutamago

verified-commit

Run lint, type-check, and tests before commits.

Community
Intermediate
changoo89changoo89
19

quality-gates

Automate pre-commit type, lint, todo, and branch validations.

Community
Advanced
tomwangowatomwangowa
1

code-review-gemini

Review staged git changes for security, logic, performance, and quality issues.

Community
Advanced
MartinNevlahaMartinNevlaha
1

run-tests

Execute project test suites and linters across Python, Node.js, and Go/Rust codebases.

Community
Intermediate