'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」。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

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

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).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

커밋 직전에 파일을 정리하고 기존 타입 검사와 테스트를 실행하도록 설정합니다. Husky와 lint-staged의 설치부터 설정 파일 작성과 동작 확인까지 다룹니다.

• 커밋 전 자동 검사 도입
• Prettier로 커밋 대상 파일 정리
• 기존 타입 검사와 테스트 실행

Claude Code에서 파일을 편집할 때 Plankton으로 자동 서식 정리와 코드 검사를 실행하도록 설정합니다. 남은 위반의 자동 수정과 재검사, 검사 규칙 보호도 다룹니다.

• 편집할 때마다 서식 정리와 코드 검사를 할 때
• 남은 검사 위반의 자동 수정을 설정할 때
• 검사 규칙이 완화되는 것을 막을 때

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

기능 추가나 리팩터링 후 빌드, 타입, lint, 테스트, 비밀 정보 검색, 변경 차이를 여섯 단계로 확인합니다. 통과 여부와 수정 사항, PR 준비 상태를 보고합니다.

• 기능 추가 후 코드를 검증합니다
• 리팩터링 후 문제를 확인합니다
• PR 생성 전 준비 상태를 확인합니다

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

Maintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .codex/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix the trigger descriptions", "make this change and validate it", "release brooks-lint", "bump and publish", and follow-ups: "re-run", "re-validate", "update that skill", "redo the audit", "do the X part again". Do NOT trigger for: USING the brooks-lint analysis skills on some target codebase (that's brooks-review / brooks-audit / brooks-debt / brooks-test / brooks-health / brooks-sweep); generic questions about brooks-lint that don't ask to change it; or maintenance of a different plugin.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Maintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .claude/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix the trigger descriptions", "make this change and validate it", "release brooks-lint", "bump and publish", and follow-ups: "re-run", "re-validate", "update that skill", "redo the audit", "do the X part again". Do NOT trigger for: USING the brooks-lint analysis skills on some target codebase (that's brooks-review / brooks-audit / brooks-debt / brooks-test / brooks-health / brooks-sweep); generic questions about brooks-lint that don't ask to change it; or maintenance of a different plugin.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

.github/workflows/*.yml を自動解析し、CI で定義されたチェックをローカル実行する汎用スキル。 lint・fmt・test・build・audit 等に限定せず、ワークフローの run ステップを抽出して実行する。 エラーがあれば修正し、再実行して確認する。 Use when: CI を通したい、lint/test を実行したい、CI チェックしたい、 ワークフローをローカルで試したい。 Triggers: "CI", "ci-check", "lint", "test", "format", "fmt", "audit", "チェック", "検証", "CI 通して", "テスト実行", "ビルド確認"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Go バックエンドの品質チェック（golangci-lint + Swagger 生成）。「lint」「golangci-lint」「静的解析」「swagger」「OpenAPI」「ドキュメント生成」などのキーワードで自動適用。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.