“linter”的搜索结果

Discover and run the linters and format checks relevant to changed code. Use after code edits or when the user asks for lint, formatting, or static-analysis validation.

中文简介正在准备中。当前显示原文说明。

Run the project's own tests, linter, type checker and build, and report what actually failed.

中文简介正在准备中。当前显示原文说明。

Up-to-date Zig programming language patterns for version 0.17.0-dev (0.16.0 stable APIs plus the 0.17 deltas). Use when writing, reviewing, or debugging Zig code, working with build.zig and build.zig.zon files, or using comptime metaprogramming. Critical for avoiding outdated patterns from training data - especially std.net→std.Io.net (requires Io instance), std.time timestamps removed (use clock_gettime), std.Thread.Mutex/Condition/sleep removed (use pthreads), std.crypto.random removed, build system APIs (root_module, Compile methods→Module methods), I/O APIs (buffered writer pattern), container initialization (.empty/.init), allocator selection (DebugAllocator), ArrayList now unmanaged by default, @typeInfo lowercase fields (.@"struct" not .Struct), and removed language features (async/await, usingnamespace). Also covers 0.17.0-dev deltas: b.args→run_cmd.addPassthruArgs(), std.gpu→std.spirv, @bitCast logical-bit (endian-agnostic) semantics, build configurer/maker split, and the zig-pkg/ package directory. Also covers quality tooling Zig does not ship: coverage with kcov (and why in-file tests wreck the denominator), detecting unused private functions (neither the compiler nor zlint's unused-decls finds them), duplicate detection with jscpd, zlint (NOT the same-named X.509 linter in Homebrew), and the built-in fuzzer whose testOne now takes *std.testing.Smith rather than []const u8.

中文简介正在准备中。当前显示原文说明。

Harvests a DESIGN.md from an existing codebase, critiques it against the actual code, and applies safe quick-win fixes. Three modes harvest / critique / fix. Shells out to `npx @google/design.md lint` for structural validation; never reimplements Google's linter. The on-ramp that makes DESIGN.md adoptable for every existing repo, not just greenfield projects.

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

Run all project linters (ruff, mypy, sqlfluff) and report results. Invoke with /lint.

中文简介正在准备中。当前显示原文说明。

Use when running the package's skill linter against all skills and rules to validate frontmatter, required sections, and execution metadata.

中文简介正在准备中。当前显示原文说明。

Rebuild the canon mirror for a second coding agent (AGENTS.md) after a rules-file version bump: show the changelog delta, write in only the new rules, then enforce the size cap, version stamp, structural anchors, a copy into the shared folder and the linter run. Triggers: "/codex-mirror", "update the codex mirror", "AGENTS.md is stale".

中文简介正在准备中。当前显示原文说明。

Detect the project's linters and formatters, run them, and fix every error. Use when asked to lint or clean up style and type errors.

中文简介正在准备中。当前显示原文说明。

Refactor given method `${input:methodName}` to reduce its cognitive complexity to `${input:complexityThreshold}` or below, by extracting helper methods. Use when a method exceeds a cognitive-complexity threshold flagged by a linter or review.

中文简介正在准备中。当前显示原文说明。

Analyze a project's harness maturity and guide staged adoption of Harness Engineering best practices (quality loops, safety gates, linters, CLAUDE.md optimization).

中文简介正在准备中。当前显示原文说明。

Maintain a support docs pack — dedup, length budgets, and no splintering — and land changes as a reviewed pull request. Use when a support thread, or a hand-off from Support assist, surfaces a new resolution, a correction to an existing one, or a deployment quirk worth recording. Not for ordinary code changes.

中文简介正在准备中。当前显示原文说明。

Use when reviewing local staged or unstaged implementation changes for a .plans/ROADMAP.md item in this repository. Performs a static-only code review without running tests, linters, builds, formatters, or app commands; checks roadmap alignment, .plans/DEVIATIONS.md quality, TypeScript/API boundary design, and React implementation quality.

中文简介正在准备中。当前显示原文说明。

Run all available tests and linters, check for anti-patterns, and generate a comprehensive code quality report

中文简介正在准备中。当前显示原文说明。

Mojibake-Reparatur für doppelt/dreifach kodiertes UTF-8. Behebt Windows-cp1252/Latin-1-Fehlinterpretationen. Ohne Abhängigkeiten.

中文简介正在准备中。当前显示原文说明。

Baut und betreibt ein anbieterneutrales Self-Care-Kernset für geplante LLM-Aufgaben und Desktop-App-Automationen. Ergänzt deterministisches Policy-Linting, Lock- und Modell-Governance, semantische Prompt-Prüfung, konsistente Mehrflächen-Updates, Mini-Checks und Regeldatei-Hygiene. Nutzen, wenn ein Agent seinen nativen Scheduler entdecken oder eine bestehende Automations-Flotte mit Rollback, Readback und Löschschutz kontinuierlich verbessern soll. Löst aus bei automation self-care, Scheduler-Task-Pflege, Desktop-App-Automations-Wartung, Automations-Flotten-Audit, selbstheilende Zeitpläne, core-set-textautomations, basic-text-automations, textbased-automation-core, textbased-automation-drivers, textbased-governance-automations oder textbased-desktopapp-automations.

中文简介正在准备中。当前显示原文说明。

Google TypeScript Style Guide reference for writing, reviewing, and refactoring TypeScript code. Use this skill whenever you are writing TypeScript code, reviewing TypeScript code, refactoring TypeScript, configuring ESLint or linter rules for TypeScript, or when the user asks about TypeScript coding conventions, naming conventions, type system best practices, or import/export patterns. Also trigger when the user mentions 'Google style', 'gts', 'TypeScript style guide', or asks 'how should I name this', 'should I use interface or type', 'how to handle null/undefined' in a TypeScript context. TypeScriptを書く・レビューする・リファクタリングする、ESLintの設定をする、「命名規則」「型の使い方」「import/exportのルール」「interfaceとtypeどっち」「anyを使っていい？」「nullチェックどうする」「Google式」「コーディング規約」「スタイルガイド」などの質問にも対応します。TypeScriptのコードに関する質問や作業であれば積極的にこのスキルを使ってください。

中文简介正在准备中。当前显示原文说明。

Validate Claude Code skills against the agentskills specification. Catches structural, semantic, and naming issues before users do.

中文简介正在准备中。当前显示原文说明。

Automate doc generation with JSDoc/TSDoc, linters, and pre-commit hooks. Use when setting up markdownlint, configuring doc linting pipelines, integrating JSDoc/TSDoc, or building automated documentation workflows.

中文简介正在准备中。当前显示原文说明。

Diagnose data races, convert callback-based code to async/await, implement actor isolation patterns, resolve Sendable conformance issues, and guide Swift 6 migration. Use when developers mention: (1) Swift Concurrency, async/await, actors, or tasks, (2) "use Swift Concurrency" or "modern concurrency patterns", (3) migrating to Swift 6, (4) data races or thread safety issues, (5) refactoring closures to async/await, (6) @MainActor, Sendable, or actor isolation, (7) concurrent code architecture or performance optimization, (8) concurrency-related linter warnings (SwiftLint or similar; e.g. async_without_await, Sendable/actor isolation/MainActor lint).

中文简介正在准备中。当前显示原文说明。

Biome (Rust 製フォーマッター・リンター) リファレンス。 JavaScript / TypeScript / JSX / CSS / JSON / GraphQL / HTML (Vue, Svelte, Astro) 対応。 biome.json, biome check / lint / format / ci / migrate / upgrade, linter ルール・preset・domains, GritQL プラグイン, assist (organizeImports), suppressions (biome-ignore), LSP / VS Code / Zed, ESLint / Prettier 移行, monorepo, CI。

中文简介正在准备中。当前显示原文说明。

Audita calidad de código Kotlin/Spring Boot en este proyecto. Úsalo cuando el usuario pida revisar código, verificar estándares, hacer un code review, auditar calidad, ejecutar linters, verificar cobertura, o antes de hacer commit/PR. También úsalo cuando mencionen KTLint, Detekt, JaCoCo, cobertura, o simplemente digan "revisa el código" / "está listo para commit" / "qué tan bueno está el código".

中文简介正在准备中。当前显示原文说明。

Establish and enforce coding standards, best practices, and architectural patterns across the codebase using linters, formatters, and code review processes. Use when setting up ESLint/Prettier, configuring linting rules, creating code style guides, implementing pre-commit hooks, establishing naming conventions, enforcing TypeScript strict mode, maintaining consistency, conducting architecture reviews, or defining team coding standards.

中文简介正在准备中。当前显示原文说明。

Validate skill files for structural compliance and behavioral correctness. Four modes: static linter, spec, category rubric, audit.

中文简介正在准备中。当前显示原文说明。