antfu
antfuAnthony Fu's opinionated tooling and conventions for JavaScript/TypeScript projects. Use when setting up new projects, configuring ESLint/Prettier alternatives, monorepos, library publishing, or when the user mentions Anthony Fu's preferences.
TypeScript Conventions
exceptionlessTypeScript coding standards for the Exceptionless frontend. Naming, imports, error handling, ESLint/Prettier configuration, and type safety. Keywords: TypeScript, ESLint, Prettier, naming conventions, kebab-case, named imports, type guards, interfaces, avoid any, Promise handling, try catch, braces
1k-code-quality
OneKeyHQCode quality standards — lint (eslint/oxlint), type check (tsc), pre-commit hooks, and comment conventions. All comments must be in English.
eslint-gen
openclawGenerate ESLint config from your codebase patterns. Use when setting up linting.
eslint-config-gen
openclawGenerate ESLint config that matches your code style. Use when setting up linting.
windsurf-linting-config
jeremylongshoreConfigure and enforce code quality with AI-assisted linting. Activate when users mention "configure linting", "eslint setup", "code quality rules", "linting configuration", or "code standards". Handles linting tool configuration. Use when configuring systems or services. Trigger with phrases like "windsurf linting config", "windsurf config", "windsurf".
vercel-policy-guardrails
jeremylongshoreImplement Vercel lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Vercel integrations, implementing pre-commit hooks, or configuring CI policy checks for Vercel best practices. Trigger with phrases like "vercel policy", "vercel lint", "vercel guardrails", "vercel best practices check", "vercel eslint".
windsurf-policy-guardrails
jeremylongshoreImplement Windsurf lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Windsurf integrations, implementing pre-commit hooks, or configuring CI policy checks for Windsurf best practices. Trigger with phrases like "windsurf policy", "windsurf lint", "windsurf guardrails", "windsurf best practices check", "windsurf eslint".
perplexity-policy-guardrails
jeremylongshoreImplement Perplexity lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Perplexity integrations, implementing pre-commit hooks, or configuring CI policy checks for Perplexity best practices. Trigger with phrases like "perplexity policy", "perplexity lint", "perplexity guardrails", "perplexity best practices check", "perplexity eslint".
retellai-policy-guardrails
Implement Retell AI lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Retell AI integrations, implementing pre-commit hooks, or configuring CI policy checks for Retell AI best practices. Trigger with phrases like "retellai policy", "retellai lint", "retellai guardrails", "retellai best practices check", "retellai eslint".
replit-policy-guardrails
Implement Replit lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Replit integrations, implementing pre-commit hooks, or configuring CI policy checks for Replit best practices. Trigger with phrases like "replit policy", "replit lint", "replit guardrails", "replit best practices check", "replit eslint".
clay-policy-guardrails
Implement Clay lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Clay integrations, implementing pre-commit hooks, or configuring CI policy checks for Clay best practices. Trigger with phrases like "clay policy", "clay lint", "clay guardrails", "clay best practices check", "clay eslint".
firecrawl-policy-guardrails
Implement FireCrawl lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for FireCrawl integrations, implementing pre-commit hooks, or configuring CI policy checks for FireCrawl best practices. Trigger with phrases like "firecrawl policy", "firecrawl lint", "firecrawl guardrails", "firecrawl best practices check", "firecrawl eslint".
supabase-policy-guardrails
jeremylongshoreImplement Supabase lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Supabase integrations, implementing pre-commit hooks, or configuring CI policy checks for Supabase best practices. Trigger with phrases like "supabase policy", "supabase lint", "supabase guardrails", "supabase best practices check", "supabase eslint".
exa-policy-guardrails
Implement Exa lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Exa integrations, implementing pre-commit hooks, or configuring CI policy checks for Exa best practices. Trigger with phrases like "exa policy", "exa lint", "exa guardrails", "exa best practices check", "exa eslint".
moai-lang-javascript
modu-aiJavaScript ES2024+ development specialist covering Node.js 22 LTS, Bun 1.x (serve, SQLite, S3, shell, test), Deno 2.x, testing (Vitest, Jest), linting (ESLint 9, Biome), and backend frameworks (Express, Fastify, Hono). Use when developing JavaScript APIs, web applications, or Node.js projects.
typescript
alinaqiTypeScript strict mode with eslint and jest
static-analysis-runner
a5c-aiRun static analysis tools including SonarQube, ESLint, and multi-language linters
sast-analyzer
a5c-aiStatic Application Security Testing orchestration and analysis. Execute Semgrep, Bandit, ESLint security plugins, CodeQL, and other SAST tools. Parse, prioritize, and deduplicate findings across multiple tools with remediation guidance.
eslint
a5c-aiESLint configuration, custom rules, and plugin development.
port-rule
Port ESLint rules to rslint (a Go-based linter). Use when users want to port/migrate/implement an ESLint rule, add a new lint rule, or mention "port rule" or specific ESLint rule names like "no-unused-vars", "no-console", etc. Supports both single-rule and batch-rule porting. This skill guides through the complete workflow from setup to PR submission.
git-hooks
Prorise-coolCentral authority on git hook implementations, modern best practices, and tooling for .NET/C#, JavaScript/TypeScript, Python, and polyglot repositories. Covers framework selection (Husky.Net, lefthook, Husky, pre-commit), setup workflows, Conventional Commits, semantic versioning, secret scanning (gitleaks, TruffleHog), performance optimization, CI/CD integration, testing strategies, and team collaboration patterns. Adaptive to project scale from solo developers to enterprise teams. Use for setting up git hooks, configuring pre-commit/commit-msg/pre-push hooks, integrating dotnet format/dotnet test, ESLint/Prettier, Black/Ruff/mypy, commitlint, choosing between frameworks, optimizing hook performance, enforcing code quality, automating testing, and troubleshooting hook issues.
code-quality
jimmykaneAnalyze code quality using ESLint and project-specific patterns
fix-errors
MelvynxFix all ESLint and TypeScript errors with parallel processing using snipper agents
ln-741-linter-configurator
levnikolaevichConfigures ESLint, Prettier, Ruff, and .NET analyzers
eslint-configuration
TheBushidoCollectiveUse when eSLint configuration including config files, extends, plugins, and environment setup.
eslint-custom
TheBushidoCollectiveUse when custom ESLint rules and plugins including rule development, AST traversal, and publishing.
prettier-integration
TheBushidoCollectiveUse when prettier integration with editors, pre-commit hooks, ESLint, and CI/CD pipelines.
eslint-rules
TheBushidoCollectiveUse when eSLint built-in rules including rule configuration, severity levels, and disabling strategies.
standards-enforcement
korallisEstablish 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.
eslint-checker
jmaglyRun ESLint for JavaScript/TypeScript code quality and style enforcement. Use for static analysis and auto-fixing.
eslint-detector
alex-popov-techDetects ESLint configuration and available commands in a repository. Returns structured JSON output designed for consumption by the quality-gates-linter agent. Checks for ESLint config files, extracts lint commands from package.json, Makefile, and CLAUDE.md, and provides command sources for the agent to read directly.
obsidian
gapmissComprehensive guidelines for Obsidian.md plugin development including all 27 ESLint rules, TypeScript best practices, memory management, API usage (requestUrl vs fetch), UI/UX standards, and submission requirements. Use when working with Obsidian plugins, main.ts files, manifest.json, Plugin class, MarkdownView, TFile, vault operations, or any Obsidian API development.
Custom Static Analysis Rules
PramodDuttaWriting custom static analysis rules for ESLint, Semgrep, and SonarQube to enforce project-specific code quality and security standards.
ultracite
secondskyUltracite multi-provider linting/formatting (Biome, ESLint, Oxlint). Use for v6/v7 setup, provider selection, Git hooks, MCP integration, AI hooks, migrations, or encountering configuration, type-aware linting, monorepo errors.
eslint-plugin-configs
anchildress1Generate or update an ESLint plugin that exports rule configs compatible with ESLint v8 (eslintrc) and ESLint v9 (flat config).
custom-linter-creator
j5ik2oA skill to create custom lint rules by leveraging each programming language's existing linter ecosystem. This is a linter intended for AI agents rather than humans: error messages are designed to act as fix-instruction prompts for an AI. Create custom rules in the lints/ directory using the standard per-language methods (e.g., Rust (dylint), TypeScript/JavaScript (ESLint), Python (pylint), Go (golangci-lint)). Use cases: (1) when you want to force project-specific coding rules on an AI, (2) when you want lint rules that output AI-readable fix instructions on violation, (3) when you want to enforce naming conventions, structural patterns, or consistency rules via AI-driven linting. Triggers: "create a linter rule", "add a lint rule", "enforce this pattern", "AI linter", "custom lint", "code rules", "naming rule", "structure rule".
grey-haven-code-style
greyhaven-aiApply Grey Haven Studio's TypeScript/React and Python/FastAPI coding standards from production templates. Use when writing code, reviewing PRs, fixing linting errors, formatting files, or when the user mentions 'code standards', 'Grey Haven style', 'linting', 'Prettier', 'ESLint', 'Ruff', 'formatting rules', or 'coding conventions'. Includes exact Prettier/ESLint/Ruff configs, naming conventions, project structure, and multi-tenant database patterns.
typescript-quality-checker
matteocervelliValidate TypeScript/JavaScript code quality with ESLint, Prettier, type checking, and security analysis. Use for TypeScript/JS codebases to ensure code quality and standards.
lint-check
mehdicRun code quality linters when reviewing code. Checks style, complexity, and best practices. Supports Python (ruff), JavaScript (eslint), Go (golangci-lint), Ruby (rubocop), Java (Checkstyle/PMD). Use when reviewing any code changes for quality issues.
biome
bobmatnycBiome - Fast all-in-one toolchain for web projects (linter + formatter in Rust, 100x faster than ESLint)
eslint-prettier-config
patricio0312revConfigures ESLint and Prettier for consistent code quality with TypeScript, React, and modern best practices. Use when users request "ESLint setup", "Prettier config", "linting configuration", "code formatting", or "lint rules".
lint-project
eduhub-orgRun ESLint on the EduHub frontend. Use when the user asks to lint code, check code style, fix lint errors, or run eslint.
code-formatter-installer
patricio0312revInstalls and configures Prettier, ESLint, EditorConfig, and other code quality tools to enforce consistent code style across the team. Generates config files, npm scripts, editor settings recommendations, and CI integration suggestions. Use when users request "setup prettier", "add eslint", "configure code formatting", or "enforce code style".
Build Fix
nahisahoAnalyzes build errors and iteratively fixes them. Supports TypeScript, ESLint, and dependency errors.
biome-tooling
laurigatesBiome all-in-one formatter and linter for JavaScript, TypeScript, JSX, TSX, JSON, and CSS. Zero-config setup, 15-20x faster than ESLint/Prettier. Use when working with modern JavaScript/TypeScript projects, setting up formatting/linting, or migrating from ESLint+Prettier to a faster alternative.
biome
TerminalSkillsAssists with formatting and linting JavaScript, TypeScript, JSX, JSON, and CSS using Biome. Use when replacing ESLint and Prettier with a single fast tool, configuring lint rules, setting up CI checks, or migrating from existing linter configurations. Trigger words: biome, linter, formatter, code quality, lint, eslint replacement.
CI Log Interpretation
shopwareLabsKnowledge for interpreting CI failure logs from GitHub Actions. Covers PHPUnit, PHPStan, ECS, ESLint, TypeScript, Stylelint, Prettier, Jest, Playwright, ludtwig, and Lighthouse. Use this skill whenever reading CI logs, diagnosing why a CI check failed, analyzing GitHub Actions job output, debugging a red build, or when the user asks "why did CI fail", "what broke the build", "check the pipeline", or shares log output that contains tool errors. Also use when fetching or reviewing run logs, job logs, or check annotations from GitHub Actions, even if the user does not explicitly mention "CI" — any interaction with GitHub Actions failure output benefits from this skill's noise-filtering and tool-identification knowledge.