code-quality
Skill1 starsChanged 8 months agoMITView on GitHub
ESLint + Prettier + Husky + lint-staged の統合セットアップを自動化するスキル。 プロジェクトの技術スタックを自動検出し、最適な設定を生成する。 既存設定がある場合はユーザーに確認: 「既存の設定を上書きしますか?それともマージしますか?」 TypeScript プロジェクト: JavaScript プロジェクト: TypeScript でない場合は typecheck と quality から typecheck を除外。
- Installs packages
77 other projects use a version of this.
Adopted by
Most recently taken up by
- magnusrodseth/dotfilestheir own version, first seen Nov 8, 2026
- KadirHarmanc/nazar-skilltheir own version, first seen Nov 8, 2026
- AndersonAndrad/skillstheir own version, first seen Nov 8, 2026
- Mehul72/skillstheir own version, first seen Nov 8, 2026
- eea/eea.agent.skillstheir own version, first seen Nov 8, 2026
- notque/vexjoy-agenttheir own version, first seen Nov 7, 2026
Used with
Projects with it also use spring-boot, logging-patterns and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ffsshhttiikkSkillspring-boot
Spring Boot framework and Java enterprise patterns
Also in 3 projects that use this
DIL8654Skilllogging-patterns
Keep logs structured, correlated, low-noise, and safe for production support. Use when adding operational logging, reviewing observability, or improving diagnostics in .NET services.
Also in 3 projects that use this
mstuder-slalomSkilljpa-patterns
JPA/Hibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot.
Also in 3 projects that use this
ffsshhttiikkSkilldesign-patterns
Practical application and coding skills for Design Patterns
Also in 4 projects that use this
glommerSkillpr-workflow
General guidelines for Commits, formatting, CI, dependencies, security
Also in 4 projects that use this
vm0-aiSkillcli-design
Design patterns and conventions for the Okou CLI user experience
Also in 3 projects that use this
Other versions77 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 77
- tursodatabase/turso★ 25ksame name
- superdesigndev/treg★ 7.7ksame name
- doorkeeper-gem/doorkeeper★ 5.5ksame name
- static-web-server/static-web-server★ 2.4ksame name
- piomin/claude-ai-spring-boot★ 1.4ksame name
- microsoft/winappCli★ 1.4ksame name
- glommer/pgmicro★ 1.2ksame name
- vm0-ai/vm0★ 1.2ksame name
- rommapp/argosy-launcher★ 710same name
- waybarrios/opencode-power-pack★ 547same name
67 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- my_pm_toolsSkill
- ci-cd-pipelineSkill
- git-workflowSkill
- project-setup-automationSkill
- typescript-best-practicesSkill
- workspace-bridgeSkill
The file
Files
コード品質ツールチェーン導入スキル
メタデータ
- トリガー: 「コード品質を設定したい」「ESLint導入」「Prettier設定」「lint-staged」「Husky設定」「コード品質ツールチェーン」
- 前提条件: Node.js プロジェクト(package.json が存在)
概要
ESLint + Prettier + Husky + lint-staged の統合セットアップを自動化するスキル。 プロジェクトの技術スタックを自動検出し、最適な設定を生成する。
Phase 1: プロジェクト検出
1.1 技術スタック判定
# package.json の存在確認
cat package.json
# TypeScript 判定
[ -f tsconfig.json ] && echo "TypeScript" || echo "JavaScript"
# フレームワーク判定
node -e "
const pkg = require('./package.json');
const deps = {...(pkg.dependencies||{}), ...(pkg.devDependencies||{})};
if (deps.next) console.log('Next.js');
else if (deps.react) console.log('React');
else if (deps.vue) console.log('Vue');
else if (deps.express) console.log('Express');
else console.log('Node.js');
"1.2 既存ツール確認
# 既存の lint/format 設定を確認
ls -la .eslintrc* eslint.config.* .prettierrc* .prettierignore biome.json 2>/dev/null
ls -la .husky/ 2>/dev/null既存設定がある場合はユーザーに確認: 「既存の設定を上書きしますか?それともマージしますか?」
Phase 2: パッケージインストール
2.1 ESLint + Prettier(標準構成)
# TypeScript プロジェクトの場合
npm install --save-dev \
eslint \
@eslint/js \
typescript-eslint \
prettier \
eslint-config-prettier \
eslint-plugin-prettier \
globals
# JavaScript プロジェクトの場合
npm install --save-dev \
eslint \
@eslint/js \
prettier \
eslint-config-prettier \
eslint-plugin-prettier \
globals2.2 フレームワーク固有プラグイン
# React / Next.js の場合
npm install --save-dev eslint-plugin-react eslint-plugin-react-hooks eslint-plugin-jsx-a11y
# Vue の場合
npm install --save-dev eslint-plugin-vue2.3 Husky + lint-staged
npm install --save-dev husky lint-staged
npx husky initPhase 3: 設定ファイル生成
3.1 ESLint 設定(Flat Config — eslint.config.mjs)
TypeScript プロジェクト:
import eslint from '@eslint/js';
import tseslint from 'typescript-eslint';
import prettierConfig from 'eslint-config-prettier';
import globals from 'globals';
export default tseslint.config(
eslint.configs.recommended,
...tseslint.configs.recommended,
prettierConfig,
{
languageOptions: {
globals: {
...globals.node,
...globals.browser,
},
},
rules: {
'@typescript-eslint/no-unused-vars': ['error', { argsIgnorePattern: '^_' }],
'@typescript-eslint/no-explicit-any': 'warn',
'no-console': 'warn',
},
},
{
ignores: ['dist/', 'build/', 'node_modules/', 'coverage/', '*.config.js', '*.config.mjs'],
}
);JavaScript プロジェクト:
import eslint from '@eslint/js';
import prettierConfig from 'eslint-config-prettier';
import globals from 'globals';
export default [
eslint.configs.recommended,
prettierConfig,
{
languageOptions: {
globals: {
...globals.node,
...globals.browser,
},
},
rules: {
'no-unused-vars': ['error', { argsIgnorePattern: '^_' }],
'no-console': 'warn',
},
},
{
ignores: ['dist/', 'build/', 'node_modules/', 'coverage/'],
},
];3.2 Prettier 設定(.prettierrc)
{
"semi": true,
"trailingComma": "es5",
"singleQuote": true,
"printWidth": 100,
"tabWidth": 2,
"endOfLine": "lf"
}3.3 .prettierignore
dist/
build/
node_modules/
coverage/
*.min.js
*.min.css
package-lock.json3.4 Husky pre-commit フック(.husky/pre-commit)
npx lint-staged3.5 lint-staged 設定(package.json に追加)
{
"lint-staged": {
"*.{ts,tsx,js,jsx}": ["eslint --fix", "prettier --write"],
"*.{json,md,yml,yaml,css,scss}": ["prettier --write"]
}
}3.6 package.json scripts 追加
{
"scripts": {
"lint": "eslint .",
"lint:fix": "eslint . --fix",
"format": "prettier --write .",
"format:check": "prettier --check .",
"typecheck": "tsc --noEmit",
"quality": "npm run lint && npm run format:check"
}
}TypeScript でない場合は typecheck と quality から typecheck を除外。
Phase 4: 動作確認
4.1 リントテスト
npm run lint 2>&1 | head -20
npm run format:check 2>&1 | head -204.2 Git フック確認
# テストコミットで pre-commit フックが動作するか確認
echo "// test" >> /tmp/test.js
git add /tmp/test.js 2>/dev/null || true4.3 問題修正
エラーが出た場合:
eslint --fix .で自動修正可能なものを修正prettier --write .でフォーマット修正- 残りの手動修正が必要なものをユーザーに報告
Phase 5: CI 連携
5.1 GitHub Actions に品質チェックステップ追加
既存の .github/workflows/ci.yml がある場合、以下のステップを追加提案:
- name: Lint
run: npm run lint
- name: Format Check
run: npm run format:check
- name: Type Check
run: npm run typecheck完了チェックリスト
| # | 確認項目 | 状態 |
| 1 | eslint.config.mjs が存在する | |
| 2 | .prettierrc が存在する | |
| 3 | .prettierignore が存在する | |
| 4 | .husky/pre-commit が存在する | |
| 5 | lint-staged が package.json に設定されている | |
| 6 | npm run lint が正常動作する | |
| 7 | npm run format:check が正常動作する | |
| 8 | pre-commit フックが動作する |
Biome 代替オプション
Biome(Rust製の高速リンター+フォーマッター)を選択する場合:
npm install --save-dev @biomejs/biome
npx biome initBiome は ESLint + Prettier の代替として使用可能。新規プロジェクトや速度重視の場合に推奨。 既存の ESLint プラグインエコシステムが必要な場合は ESLint + Prettier を推奨。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

