Results for “lint”

各プログラミング言語の既存リンターエコシステムを活用してカスタムlintルールを作成するスキル。 人間向けではなくAIエージェント向けのリンターであり、エラーメッセージはAIに対する修正指示プロンプトとして機能する。 Rust(dylint)、TypeScript/JavaScript(ESLint)、Python(pylint)、Go(golangci-lint)等、 言語ごとの標準的な方法でカスタムルールを `lints/` ディレクトリに作成する。 以下の場合に使用する: (1) プロジェクト固有のコーディングルールをAIに強制させたいとき、 (2) 違反時にAIが読める修正指示を出力するlintルールを作りたいとき、 (3) 命名規則・構造パターン・一貫性ルールをAI駆動のリンティングで強制したいとき。 トリガー: 「リンタールールを作成」「lintルールを追加」「このパターンを強制」 「AIリンター」「カスタムlint」「コードルール」「命名ルール」「構造ルール」 「create a linter rule」「add a lint rule」「enforce this pattern」「AI linter」。

The English summary is being prepared. Showing the original description.

Set up ESLint, a tool that checks JavaScript for errors and coding rule violations. Configure shared rules, connect checks to editors and automated workflows, and review flagged code alongside its behavior in the browser.

• Setting up ESLint for a JavaScript project
• Applying consistent coding rules across a team
• Adding code checks to editors and CI/CD

Turn a code pattern fixed in a pull request into a custom Go linter, a tool that checks code without running it. Covers a focused detection rule, tests, and registration in the linter runner.

• Turning a PR fix into a repeatable code check
• Adding a custom Go linter
• Testing cases that should and should not be flagged

Check out a GitHub pull request, fix linting and TypeScript errors, and commit and push the changes. The workflow supports forked pull requests and repeats type checks to verify fixes while keeping changes focused on these errors.

• Fix linting errors in a pull request
• Resolve TypeScript errors in a pull request
• Apply fixes to a pull request from a fork

Install, configure, or update anti-slop plugins for Oxlint, a code checking tool. Preserves local customizations in copied plugin code while aligning dependency versions, merging configuration, running checks, and recording the installed source.

• Install anti-slop rules in an Oxlint project
• Update copied plugins while preserving local changes
• Configure lint and format exclusions for Vite+

Linting best practices and golangci-lint configuration for Golang projects — running linters, configuring .golangci.yml, suppressing warnings with nolint directives, interpreting lint output, and selecting linters. Use when configuring golangci-lint, asking about lint warnings or nolint suppressions, setting up code quality tooling, or choosing linters. Also use when the user mentions golangci-lint, go vet, staticcheck, or revive. Not for wiring a lint step into a GitHub Actions pipeline (→ See `samber/cc-skills-golang@golang-continuous-integration` skill).

The English summary is being prepared. Showing the original description.

Run and configure oxlint — the high-performance JavaScript/TypeScript linter built on the Oxc compiler stack. Use this skill whenever working in a project that has oxlint installed (check for `oxlint` in package.json devDependencies or an `.oxlintrc.json` / `oxlint.config.ts` config file). This includes when you need to lint code after making changes, fix linting errors, configure oxlint rules/plugins, set up or modify `.oxlintrc.json`, or migrate from ESLint.

The English summary is being prepared. Showing the original description.

Set up automated checks before each Git commit using Husky and lint-staged. Format staged files with Prettier, run existing type checks and tests, and verify the setup using the repository's package manager.

• Adding automated checks before commits
• Formatting staged files with Prettier
• Running existing type checks and tests before commits

Set up Plankton hooks in Claude Code to format and lint files after each edit. Route remaining violations to Claude for fixes, verify the results, and protect linter settings from changes that weaken checks.

• Formatting and linting files after every edit
• Setting up automatic fixes for remaining violations
• Protecting linter configuration from rule weakening

Write and review GitHub Actions workflows for syntax and structural correctness. Check quoting around expressions and special characters, then validate with actionlint, a workflow checker, to catch errors that ordinary YAML parsing can miss.

• Reviewing new or edited GitHub Actions workflow files
• Checking quotes around expressions containing special characters
• Investigating workflow failures before any jobs start

Configures and enforces SwiftLint in Swift projects using build tool plugins, run scripts, and CI. Covers .swiftlint.yml configuration, disabled_rules, opt_in_rules, only_rules, analyzer_rules, baselines, autocorrect, swiftlint:disable suppressions, reporter formats (sarif, json, checkstyle), strict and lenient modes, SwiftLintBuildToolPlugin via SimplyDanny/SwiftLintPlugins, swift package plugin swiftlint, Xcode run script phases, CI integration, multiple configuration files, and rollout strategies for existing codebases. Use when setting up SwiftLint, configuring lint rules, suppressing warnings, creating baselines, choosing between build tool plugin and run script, or integrating SwiftLint into CI.

The English summary is being prepared. Showing the original description.

Linting and code quality workflow for Software Metrics Machine. Covers ESLint 9.x flat config, Prettier formatting, lint-staged (auto-fix on commit), per-workspace configs, TypeScript strict mode, and all lint commands. USE FOR: lint, eslint, prettier, format, code style, linting, lint fix, auto-fix, check style, code quality, lint-staged, typecheck, type-check, tsc noEmit. DO NOT USE FOR: writing tests (use tdd skill), building (use build commands), commit hooks setup.

The English summary is being prepared. Showing the original description.

Verify completed code changes in six stages: build, type checks, lint, tests with coverage, searches for possible secrets, and diff review. Produces a pass/fail report with issues to fix and readiness for a pull request.

• Verifying code after completing a feature
• Checking for problems after refactoring
• Reviewing readiness before creating a pull request

Use Metalint in .NET repositories that ship Node-based frontend assets and want one CLI entrypoint over several underlying linters. USE FOR: unified frontend lint commands; combined ESLint, Stylelint, HTMLHint, or similar checks; CI orchestration over multiple frontend linters. DO NOT USE FOR: simple repos where Biome already covers the required surface; teams that have not decided which underlying linters own each file type. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

The English summary is being prepared. Showing the original description.

ESLint is the standard linting tool for JavaScript and TypeScript projects. It statically analyzes your code to find problems, enforce coding conventions, and catch bugs before they reach production. ESLint 9 introduced the flat config format, replacing the legacy `.eslintrc` system with a simpler, more composable `eslint.config.js` file. With a rich plugin ecosystem covering React, TypeScript, accessibility, and import ordering, ESLint is the backbone of code quality in modern web development.

The English summary is being prepared. Showing the original description.

ESLint is the standard linting tool for JavaScript and TypeScript projects. It statically analyzes your code to find problems, enforce coding conventions, and catch bugs before they reach production. ESLint 9 introduced the flat config format, replacing the legacy `.eslintrc` system with a simpler, more composable `eslint.config.js` file. With a rich plugin ecosystem covering React, TypeScript, accessibility, and import ordering, ESLint is the backbone of code quality in modern web development.

The English summary is being prepared. Showing the original description.

Find TypeScript values that bypass type checking through any, including inferred types and assertions. Suggest unknown, generics that preserve type relationships, or Zod validation for external data, with the checks needed where each value is used.

• Addressing ESLint warnings about explicit any
• Reviewing type safety around external API data
• Checking functions that pass any to their callers

Inspect recent merges for leftover debug code, TODO comments, lint warnings, and technical debt, meaning deferred maintenance work. Create a prioritized cleanup list that separates small fix candidates from issues requiring human judgment.

• Finding debug code left after merging
• Organizing TODO and FIXME follow-up work
• Prioritizing newly introduced lint warnings

Add custom Go code checkers to gh-aw, with guidance on tests, registration, and running all checks. Handle equivalent syntax consistently and optionally limit performance rules using test coverage, which records which code tests execute.

• Adding a custom Go code checking rule
• Testing rules against equivalent syntax forms
• Registering a checker in the shared runner

Use Stylelint in .NET repositories that ship CSS, SCSS, or other stylesheet assets alongside web frontends. USE FOR: stylelint.config.*, .stylelintrc*, CSS or SCSS assets; CSS linting; duplicate style cleanup and naming-convention checks. DO NOT USE FOR: JavaScript or TypeScript lint ownership; runtime accessibility, performance, SEO, or header checks. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

The English summary is being prepared. Showing the original description.

Use ESLint in .NET repositories that ship JavaScript, TypeScript, React, or other Node-based frontend assets. USE FOR: the repo has package.json, eslint.config.*, .eslintrc*, tsconfig.json, or JS/TS/React frontend files; the user asks for JavaScript or TypeScript linting, React rule. DO NOT USE FOR: CSS ownership by itself; route that to stylelint; HTML-only checks on static output; route that to htmlhint. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

The English summary is being prepared. Showing the original description.

SEO & GEO content linter — validates Markdown/MDX files for AI search visibility using 92 deterministic rules (35 GEO, 32 SEO, 14 content quality, 8 technical, 3 i18n). Runs an autonomous lint-fix loop: scan content, read structured violations, fix them, re-lint until clean. Use when optimizing content for AI citations, auditing SEO compliance, checking GEO readiness, or running pre-publish content validation. Triggers on: "geo-lint", "lint content", "SEO audit", "GEO", "content optimization", "AI search", "citation readiness".

The English summary is being prepared. Showing the original description.

Turn a course plan into numbered exercise folders with problem, solution, and explanation variants. Create starter readme files, check naming and links with the project’s linter, and fix structural errors before committing.

• Set up exercise folders for a new course section
• Create problem, solution, and explanation stubs
• Renumber exercises and check their structure

Standardize Chinese Git commit messages and changelogs using Conventional Commits, a structured message format. The skill provides writing rules and configuration examples for message checks, interactive commit entry, and automatic changelog generation.

• Standardizing Chinese commit messages across a team
• Checking commit formats with commitlint and husky
• Generating changelogs with Chinese section headings