'linter' 검색 결과

各プログラミング言語の既存リンターエコシステムを活用してカスタム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」。

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

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

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

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

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.

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

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.

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

検査器（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 へ委譲する

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

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

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

Writes and reviews Lean 4 proofs, machine-checked arguments for mathematics or specifications. Follows Mathlib conventions to organize definitions and lemmas, fill proof gaps, refactor lengthy proofs, and establish automated checks for unproved claims and style.

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

• Formalizing mathematics or specifications in Lean 4
• Filling sorry placeholders in proofs
• Splitting long proofs into reusable lemmas

Add and validate custom Go analysis linters in gh-aw.

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

Generate a new pkg/linters analyzer from a merged or open PR pattern.

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

Supabase security expert to audit RLS (Row Level Security), RBAC, relational databases, prevent data leakage, and utilize Supabase Linter / Ahli keamanan Supabase untuk audit RLS (Row Level Security), RBAC, database relasional, pencegahan kebocoran data, dan pemanfaatan Supabase Linter.

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

Multi-language code quality validation (Python, JS/TS, Shell, SQL) — formatting, linting, type-checking, complexity analysis with auto language detection. Use when checking code quality or running linters. Trigger on "lint", "type-check", "quality check", "run the linters", "check code quality".

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

[Quality] Use when a workflow step or the user asks for linters, formatters, type checks and static analysis in pre-commit and CI gates.

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

Code quality dashboard. Wraps existing project tools (type checker, linter, test runner, dead code detector, shell linter), computes a weighted composite 0-10 score, and tracks trends over time. Use when: "health check", "code quality", "how healthy is the codebase", "run all checks", "quality score". (gstack)

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

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

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

Prepare a repository for Claude Code on the web by creating a startup hook that installs project dependencies. Register the hook and check that it runs successfully, along with a sample test and code quality check.

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

• Prepare a repository for Claude Code on the web
• Install dependencies when a web session starts
• Check that tests and code quality tools can run

Design the operating layer around a coding agent so it can read and edit code, run checks, and correct errors. Define completion criteria, permission boundaries, feedback, and recovery methods, and assess which tasks suit autonomous execution.

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

• Designing a coding agent's tools and workflow
• Adding acceptance checks and permission boundaries
• Assessing tasks for autonomous agent execution

Set consistent Python conventions for naming, formatting, type checking, and documentation. Configure ruff and mypy or pyright, write clear function descriptions, and organize README and changelog content so a team can maintain shared standards.

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

• Set up Python linting and formatting
• Define shared team coding conventions
• Review type hints and function documentation

Review GitHub Actions workflows for unsafe input handling, excessive token permissions, exposed secrets, and changeable action references. Get findings grouped by issue type, with severity ratings, exact YAML locations, and concrete fixes to review.

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

• Reviewing CI workflows for security issues
• Checking privileged triggers that run fork code
• Restricting GITHUB_TOKEN permissions

Route product questions to a specialist for prioritization, research, analytics, experiments, or implementation. Support recurring discovery by tracking interviews and assumption tests, checking how customer needs connect to proposed solutions, and returning results with a concise digest.

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

• Prioritizing features with an explicit framework
• Planning product experiments and sample sizes
• Tracking weekly interviews and assumption tests

Build and review Kubernetes Operators, controllers that keep custom resources in their desired state. Included tools check resource definitions and Go reconciliation code, then assess operational capabilities and suggest improvements.

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

• Designing custom resource definitions for a new Operator
• Reviewing Go reconciliation code for common mistakes
• Assessing Operator capabilities and planning improvements

Review REST API specifications with automated checks for inconsistent conventions and breaking changes—changes that disrupt existing clients. Get a design grade, improvement recommendations, and tool reports to support release reviews and API migrations.

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

• Reviewing a pull request that changes API endpoints
• Checking compatibility before an API version migration
• Establishing shared API design standards

Review skill and agent definitions for structural issues and whether their instructions meet expected behavior. Four modes cover structure, test specifications, category criteria, and coverage reports that reveal missing specifications or checks.

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

• Check one skill or all skills for structural issues
• Compare skill or agent instructions with a test specification
• Review definitions against category criteria