lint

Contains commands to lint, format, type check, test, and build the project. Use when the user explicitly invokes the lint skill.

469 stars

Best use case

lint is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Contains commands to lint, format, type check, test, and build the project. Use when the user explicitly invokes the lint skill.

Teams using lint should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/lint/SKILL.md --create-dirs "https://raw.githubusercontent.com/kovrichard/catalyst/main/.agents/skills/lint/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/lint/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How lint Compares

Feature / AgentlintStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Contains commands to lint, format, type check, test, and build the project. Use when the user explicitly invokes the lint skill.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

When this skill is invoked, run the following commands in order.

`bun run check-write`: Runs linter and formatter and fixes trivial issues
`bun run type-check`: Runs type checking
`bun run test`: Runs tests
`bun run build`: Runs build

When any of the commands fail, start fixing the issues one by one instead of explaining the error.

If the output of the first command contains unsafe, but fixable errors. you may use the `bun run check-write --unsafe` command to fix them.

Related Skills

remember

469
from kovrichard/catalyst

When the user invokes this skill, the agent reflects on the most important lessons learned recently and suggests adding a new rule to AGENTS.md to prevent the same issue from recurring. Use when the user explicitly invokes the remember skill.

optimize

469
from kovrichard/catalyst

Scans the repository for optimization opportunities — complexity, performance issues, large files, and maintainability problems — and fixes them one at a time with user confirmation. Use only when the user explicitly invokes this skill.

lint-and-validate

31392
from sickn33/antigravity-awesome-skills

MANDATORY: Run appropriate validation tools after EVERY code change. Do not finish a task until the code is error-free.

Code Quality & StandardsClaude

lint-and-validate

24269
from davila7/claude-code-templates

Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis.

wiki-lint

9958
from alirezarezvani/claude-skills

Run a health check on the LLM Wiki vault — mechanical checks (orphans, broken links, stale pages, missing frontmatter, log gap, duplicates) plus semantic checks (contradictions, cross-reference gaps, concepts missing their own page). Outputs a markdown report with suggested actions. Usage /wiki-lint [--stale-days N] [--log-gap-days N]

cs-wiki-linter

9958
from alirezarezvani/claude-skills

Dispatched sub-agent that runs a periodic health check on an LLM Wiki vault. Runs mechanical checks via scripts (orphans, broken links, stale pages, missing frontmatter, duplicate titles, log gaps), does semantic checks (contradictions, stale claims, cross-reference gaps, concepts missing their own page), and produces a markdown report with suggested actions. Spawn weekly, after batch ingests, or when the user says "check the wiki" / "lint my wiki" / "audit the vault".

swiftlint

3891
from openclaw/skills

Swift linting and style enforcement via CLI

windsurf-linting-config

1868
from jeremylongshore/claude-code-plugins-plus-skills

Configure and enforce code quality with AI-assisted linting. Activate when users mention "configure linting", "eslint setup", "code quality rules", "linting configuration", or "code standards". Handles linting tool configuration. Use when configuring systems or services. Trigger with phrases like "windsurf linting config", "windsurf config", "windsurf".

golang-lint

1013
from samber/cc-skills-golang

Provides linting best practices and golangci-lint configuration for Go projects. Covers running linters, configuring .golangci.yml, suppressing warnings with nolint directives, interpreting lint output, and managing linter settings. Use this skill whenever the user runs linters, configures golangci-lint, asks about lint warnings or suppressions, sets up code quality tooling, or asks which linters to enable for a Go project. Also use when the user mentions golangci-lint, go vet, staticcheck, revive, or any Go linting tool.

lint

533
from kurtosis-tech/kurtosis

Lint and format Kurtosis Starlark files. Check syntax, validate docstrings, and auto-format .star files. Use when writing or reviewing Starlark packages to ensure code quality.

eslint

509
from a5c-ai/babysitter

ESLint configuration, custom rules, and plugin development.

tech-writing-lint

509
from a5c-ai/babysitter

Automated technical writing style and quality enforcement. Lint documentation with Vale, check for inclusive language, enforce style guides, and analyze readability metrics.