メニュー
Analyze and fix ESLint errors across the project. Use when the user asks to clean up code style, fix linting issues, or perform a quality review.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/0xkynz/codekit --skill eslint-fixコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
Guide for working with AGENTS.md — the open standard for AI coding agent configuration. Use when creating, updating, or optimizing AGENTS.md files, or when onboarding a project to multi-agent workflows.
Better Auth integration expert for TypeScript authentication — server config, client setup, database adapters, OAuth providers, plugins (2FA, organizations), session management, and security hardening. Use when adding auth to a project, configuring Better Auth, implementing login/signup flows, setting up OAuth, enabling 2FA, or securing auth endpoints.
Domain-Driven Design with Clean Architecture — framework-agnostic patterns for entities, value objects, aggregates, use cases, and the dependency rule. Use PROACTIVELY when designing domain models, implementing bounded contexts, structuring layered architectures, separating business logic from infrastructure, or applying DDD tactical patterns in any language or framework.
SKILL.md を表示中
| name | eslint-fix |
| description | Analyze and fix ESLint errors across the project. Use when the user asks to clean up code style, fix linting issues, or perform a quality review. |
| argument-hint | ["directory-or-file"] |
| context | fork |
| agent | general-purpose |
| allowed-tools | Read, Write, Bash(npx eslint ), mcp__eslint__ |
This skill provides a structured workflow for resolving linting violations while maintaining code quality and architectural consistency.
To fix all issues in the current project, simply run:
/eslint-fix
First, understand the scope of the issues. Use the analyze script to generate a report grouped by directory:
bash $SKILL_PATH/scripts/analyze_errors.sh $ARGUMENTS
Choose a strategy based on the total error count:
Direct Fix (≤ 20 errors): Iterate through files sequentially. For each file, read the content, identify the specific rule violation, and modify the code to comply.
Parallel Fix (> 20 errors): If the codebase has high-volume violations, spawn specialized subagents for each major directory to process files in parallel.
For every modification, you MUST verify the fix immediately:
npx eslint <file-path> specifically for that file.eslint-disable comments to bypass rules.Once complete, provide a report including:
// eslint-disable or modify eslint.config.js to hide errors.CLAUDE.md.