'lint' 검색 결과

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

Check GenLayer intelligent contracts before testing. This skill uses the GenVM linter to find forbidden code patterns, SDK usage errors, and type mismatches, with JSON output for repeated fixes and commands to extract contract interface definitions.

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

• Checking a contract before running tests
• Finding forbidden imports and invalid storage types
• Fixing errors repeatedly using JSON results

Set up JavaScript and TypeScript projects using Anthony Fu’s conventions for code organization, development tools, and package publishing. Establish shared checks for formatting, types, unused code, and tests before committing changes.

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

• Setting up a new TypeScript project
• Standardizing formatting and code checks
• Managing dependencies across a monorepo

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」「ドキュメント生成」などのキーワードで自動適用。

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

Code quality standards for OneKey. Use when fixing lint warnings, running pre-commit tasks, handling unused variables, writing comments, or ensuring code quality. All comments must be in English. Triggers on lint, linting, eslint, oxlint, tsc, type check, unused variable, comment, documentation, spellcheck, code quality, pre-commit, yarn lint.

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

Figma 디자인을 코드로 구현할 때 지킬 프로젝트별 규칙을 만듭니다. 색상과 간격 등의 공통값, 명명 규칙, 자동 검사 기준을 한곳에 정리합니다.

• Figma 디자인 구현 규칙 수립
• 디자인 공통값과 명명 규칙 정리
• 자동 검사 기준 통합

Review changed code against project rules and report missing tests, unused code, typing problems, and style violations. It also checks API design and data isolation, helping developers identify issues after implementation.

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

• Reviewing changes after implementation
• Finding missing tests and unused code
• Checking Python types and API design

安全诊断并修复 ESLint error、warning 和配置兼容问题。用于用户要求运行 lint、解释 ESLint 报错、限定范围自动修复或迁移 ESLint 配置时；优先使用项目锁定的包管理器与版本，先预检再修改，不自动下载最新版或批量改写无关源码。

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

Use webhint in .NET repositories that ship browser-facing frontends. Use when a repo needs CLI audits for accessibility, performance, security headers, PWA signals, SEO, or runtime page quality against a. USE FOR: the repo ships a browser-facing site and the user asks about accessibility, performance, SEO, security headers, or page quality; the repo has .hintrc, hint scripts, or a. DO NOT USE FOR: JavaScript or TypeScript semantic linting; route that to eslint or biome; stylesheet-only linting; route that to stylelint. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

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

You are an expert in Biome, the Rust-based toolchain that replaces ESLint and Prettier with a single, fast tool. You help developers configure linting, formatting, and import sorting for JavaScript, TypeScript, JSX, JSON, and CSS — achieving 100x faster execution than ESLint+Prettier with zero configuration, unified diagnostics, and IDE integration.

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

Expert guide for Biome (Rust-based linter + formatter), ESLint/Prettier migration, and code quality tooling / Panduan ahli Biome (linter + formatter berbasis Rust), migrasi dari ESLint/Prettier, dan tooling kualitas kode.

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

设计代码规范 / Lint 配置 / Code Review 标准时使用。覆盖 SOLID 原则 / Lint 工具（ESLint / Prettier / Checkstyle / pylint / golangci-lint）/ SonarQube 集成。融合 Clean Code + Robert Martin SOLID + Code Review 文化。

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

検査器（linter / ガード / CI ゲート / バリデータ / フィルタ）そのものの検出力が差分で静かに落ちていないか、また新設した検査が実際に検出できることが実証されているかを diff-time で検出する。Check 1 unverified detection reduction（検査器の検出ロジック（正規表現・除外パターン・解決集合・allowlist・baseline）を変更して検出件数が減ったのに、減った 1 件ずつが誤検出であった根拠が示されないまま「誤検出を潰した」「N → M 件に減少」と改善として主張している）、Check 2 unproven guard detection power（新しい検査ロジック・CI ゲート・バリデーションを追加・変更したのに、検出すべき入力を注入して検出されること／検出すべきでない入力で黙ることを示す変異注入の証跡が無く、「追加した」「CI が緑」を検出力の証拠として扱っている）、の 2 Check を対象とする report-only。テスト自身のアサーションが実質何も検証していない構造は test-assertion-effectiveness、レビュー基準・品質ゲートの明示的な弱体化（ルールの削除・閾値の引き下げ・suppression entry 追加・lint ルールの無効化）は review-criteria-integrity、リファクタ完了主張一般の検証は refactor-claim-audit、workflow の permissions と action pin は gha-workflow-security、設定ファイルの構文・型の妥当性は config-json へ委譲する

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

init 直後またはスタック変更時に実行。静的チェック基準カタログ（A1〜F2）を判断基準に、プロダクトへ決定的チェック（Lint / 静的解析）を選択・配線・補完し、カバレッジマップ（採否台帳）と `lint:all` コマンドを整備する。

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

Configures ESLint and Prettier for consistent code quality with TypeScript, React, and modern best practices. Use when users request "ESLint setup", "Prettier config", "linting configuration", "code formatting", or "lint rules".

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

Turn repeated corrections into automated safeguards, such as code checks, metadata flags, or scripts. This skill helps choose where each lesson belongs and turns recurring mistakes into concrete changes or actionable tasks.

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

• Preventing the same coding mistake from recurring
• Turning repeated instructions into automated checks
• Sorting corrections into notes, rules, or broader principles

Update Biome packages with pnpm, align configuration filenames and schema versions across the repository, and run the configured checks and fixes. Receive a report of remaining issues, with optional further fixes subject to agreement.

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

• Updating Biome to a specified version
• Aligning configuration files after dependency updates
• Checking for issues introduced by a Biome update

Choose and run checks for TypeScript SDK changes, including type checks, linting, builds, Vitest suites, and tests of complete runtime flows. Also guides writing or adapting CLI tests for Effect v4.

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

• Validate changes to TypeScript packages
• Choose focused checks for a change
• Investigate failing TypeScript CI checks

Run final checks on reviewed SDK changes, covering code formatting, linting for code issues, type checking, and tests. Confirm completion only after every required check succeeds, with wrappers for macOS, Linux, and Windows.

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

• Verify runtime code changes after review
• Run final checks after test or build configuration changes
• Rerun required checks after fixing a failure

Apply the same operation across multiple files using parallel worker agents. The skill finds matching files, divides the work, and reports successes, failures, and skipped files, with a preview option before edits.

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

• Add license headers across source files
• Convert JavaScript files to TypeScript
• Fix the same lint issue in multiple files

Turn a course plan into numbered exercise folders with starter readmes for problems, solutions, and explanations. Check the structure with the specified lint command, fix errors, and handle exercise moves or renaming while preserving Git history.

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

• Creating exercise folders from a course plan
• Preparing problem, solution, and explanation stubs
• Checking exercise structure and readme links