Token导航 LogoToken导航

Agent Skill · 开发

eslint-prettier-husky-config(eslint 更漂亮的哈士奇配置)

eslint-prettier-husky-config 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

eslint-prettier-husky-config 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 12,657。

总安装 1,176周安装 49GitHub Stars 3下载 392核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:eslint-prettier-husky-config(eslint 更漂亮的哈士奇配置)
来源仓库:https://github.com/hopeoverture/worldbuilding-app-skills
仓库路径:skills/eslint-prettier-husky-config
安装命令:
npx skills add https://github.com/hopeoverture/worldbuilding-app-skills --skill eslint-prettier-husky-config
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/hopeoverture/worldbuilding-app-skills --skill eslint-prettier-husky-config

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

eslint-prettier-husky-config 为 Next.js/React 项目提供完整的代码质量工具链配置,包括 ESLint v9、Prettier 与 git hooks。适用于需要统一格式化、静态检查与提交拦截的团队开发环境。支持 TypeScript 扩展与 CI 流水线集成。

安装命令:npx skills add https://github.com/hopeoverture/worldbuilding-app-skills --skill eslint-prettier-husky-config。使用前请确认是否允许安装 husky 钩子并修改 pre-commit 流程。

来源仓库内路径:skills/eslint-prettier-husky-config

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/hopeoverture/worldbuilding-app-skills --skill…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

eslint-prettier-husky-config 怎么安装?

在终端执行 npx skills add https://github.com/hopeoverture/worldbuilding-app-skills --skill eslint-pre…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

eslint-prettier-husky-config 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

eslint-prettier-husky-config 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

eslint-prettier-husky-config 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

eslint-prettier-husky-config 用的人多吗?

公开数据是累计安装 1,176 次,近一周安装 49 次,下载 392 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

eslint-prettier-husky-config 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
eslint-prettier-husky-config

eslint 更漂亮的哈士奇配置 · 本页

1,1763只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

ESLint, Prettier, Husky Configuration

Overview

Configure comprehensive code quality tooling for Next.js/React projects using ESLint v9 (flat config), Prettier, Husky git hooks, lint-staged, and CI lint checks.

Installation and Configuration Steps

1. Install Dependencies

Install required packages for ESLint v9, Prettier, and git hooks:

npm install -D eslint@^9 @eslint/js eslint-config-prettier eslint-plugin-react eslint-plugin-react-hooks eslint-plugin-jsx-a11y prettier husky lint-staged

For TypeScript projects, add:

npm install -D @typescript-eslint/parser @typescript-eslint/eslint-plugin typescript-eslint

2. Create ESLint Flat Config

Create eslint.config.mjs in project root using the provided template from assets/eslint.config.mjs. This flat config format:

  • Uses modern ESLint v9 configuration
  • Includes React, React Hooks, and JSX accessibility rules
  • Supports TypeScript with type-aware linting
  • Ignores Next.js build directories and configuration files

Customize the configuration based on project needs:

  • Adjust languageOptions.parserOptions for different ECMAScript versions
  • Modify rules to match team preferences
  • Add additional plugins as needed

3. Create Prettier Configuration

Create .prettierrc in project root using the template from assets/.prettierrc. This configuration:

  • Sets 2-space indentation
  • Uses single quotes for strings
  • Removes trailing commas
  • Sets 100-character line width
  • Uses Unix line endings

Adjust formatting rules to match team style guide.

Create .prettierignore using assets/.prettierignore to exclude:

  • Build directories (.next, dist, out)
  • Dependencies (node_modules, package-lock.json)
  • Generated files
  • Public assets

4. Set Up Husky and Lint-Staged

Initialize Husky for git hooks:

npx husky init

This creates .husky/ directory with a pre-commit hook.

Replace the pre-commit hook content with:

npx lint-staged

Add lint-staged configuration to package.json using the example from references/package-json-config.md:

{
  "lint-staged": {
    "*.{js,jsx,ts,tsx}": [
      "eslint --fix",
      "prettier --write"
    ],
    "*.{json,md,yml,yaml}": [
      "prettier --write"
    ]
  }
}

This runs ESLint and Prettier on staged files before each commit.

5. Add Package Scripts

Add the following scripts to package.json (see references/package-json-config.md for complete example):

{
  "scripts": {
    "lint": "eslint . --max-warnings 0",
    "lint:fix": "eslint . --fix",
    "format": "prettier --write .",
    "format:check": "prettier --check .",
    "prepare": "husky"
  }
}

These scripts enable:

  • npm run lint - Check for linting errors (fails on warnings)
  • npm run lint:fix - Auto-fix linting issues
  • npm run format - Format all files with Prettier
  • npm run format:check - Check formatting without modifying files
  • prepare - Automatically set up Husky when installing dependencies

6. Create GitHub Actions Lint Workflow

Create .github/workflows/lint.yml using the template from assets/github-workflows-lint.yml. This workflow:

  • Runs on pull requests and pushes to main/master
  • Checks out code and sets up Node.js
  • Installs dependencies
  • Runs both linting and format checks
  • Fails CI if any issues are found

Customize the workflow:

  • Adjust Node.js version as needed
  • Modify branch names to match repository
  • Add caching for faster CI runs

7. Verify Setup

Test the complete setup:

  1. Lint check: Run npm run lint to verify ESLint configuration
  2. Format check: Run npm run format:check to verify Prettier configuration
  3. Pre-commit hook: Make a change and commit to test Husky and lint-staged
  4. CI workflow: Push to a branch and open a PR to verify GitHub Actions

Fix any configuration issues:

  • Review ESLint errors and adjust rules if needed
  • Format all files: npm run format
  • Commit the configuration changes

8. Team Documentation

Document the setup for team members (see references/team-documentation.md for template):

  • Explain the purpose of each tool
  • Provide setup instructions for new developers
  • Document how to temporarily bypass hooks (for emergencies only)
  • Include troubleshooting steps for common issues

Configuration Customization

ESLint Rules

Adjust rule severity in eslint.config.mjs:

  • "off" - Disable rule
  • "warn" - Warning (doesn't fail CI)
  • "error" - Error (fails CI)

Common customizations:

  • Disable specific rules: 'react/prop-types': 'off'
  • Adjust rule options: 'max-len': ['error', {code: 120}]
  • Add project-specific rules

Prettier Options

Modify formatting in .prettierrc:

  • printWidth - Line length limit
  • tabWidth - Spaces per indentation level
  • semi - Semicolon preference
  • singleQuote - Quote style
  • trailingComma - Trailing comma rules

Lint-Staged Configuration

Customize pre-commit checks in package.json:

  • Add file type patterns
  • Include additional commands (tests, type checking)
  • Adjust which files trigger which linters

Example with type checking:

{
  "lint-staged": {
    "*.{ts,tsx}": [
      "eslint --fix",
      "prettier --write",
      "tsc-files --noEmit"
    ]
  }
}

Troubleshooting

ESLint errors on existing code: Run npm run lint:fix then npm run format to auto-fix most issues.

Husky hooks not running: Ensure npm install was run after Husky initialization. Check .husky/pre-commit is executable.

CI failing but local passes: Verify Node.js version matches between local and CI. Check that all dependencies are in package.json.

Conflicts between ESLint and Prettier: Ensure eslint-config-prettier is last in extends array to disable conflicting ESLint formatting rules.

Resources

scripts/

No executable scripts needed for this skill.

references/

  • package-json-config.md - Complete package.json example with all scripts and lint-staged configuration
  • team-documentation.md - Template for documenting the setup for team members

assets/

  • eslint.config.mjs - ESLint v9 flat config template with React, TypeScript, and Next.js support
  • .prettierrc - Prettier configuration with recommended settings
  • .prettierignore - Files and directories to exclude from formatting
  • github-workflows-lint.yml - GitHub Actions workflow for automated lint checks

平台分布

Codex

36.83%
按下载量换算144

Claude

29.74%
按下载量换算117

Cursor

19.31%
按下载量换算76

Gemini CLI

8.54%
按下载量换算33

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills