158 skills · sorted by relevance
Check out a GitHub pull request, fix linting and TypeScript errors, and commit and push the changes. The workflow supports forked pull requests and repeats type checks to verify fixes while keeping changes focused on these errors.
Set up Plankton hooks in Claude Code to format and lint files after each edit. Route remaining violations to Claude for fixes, verify the results, and protect linter settings from changes that weaken checks.
Set consistent Python conventions for naming, formatting, type checking, and documentation. Configure ruff and mypy or pyright, write clear function descriptions, and organize README and changelog content so a team can maintain shared standards.
Choose and run checks for TypeScript SDK changes, including type checks, linting, builds, Vitest suites, and tests of complete runtime flows. Also guides writing or adapting CLI tests for Effect v4.
Linting and formatting for Megatron-LM. Covers running autoformat.sh, tools (ruff, black, isort, pylint, mypy), and code style rules.
The English summary is being prepared. Showing the original description.
Use webhint in .NET repositories that ship browser-facing frontends. Use when a repo needs CLI audits for accessibility, performance, security headers, PWA signals, SEO, or runtime page quality against a. USE FOR: the repo ships a browser-facing site and the user asks about accessibility, performance, SEO, security headers, or page quality; the repo has .hintrc, hint scripts, or a. DO NOT USE FOR: JavaScript or TypeScript semantic linting; route that to eslint or biome; stylesheet-only linting; route that to stylelint. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
The English summary is being prepared. Showing the original description.
Configures pre-commit hooks for linting, type checking, formatting, and testing. Use when setting up a new project or adding quality gates to an existing one.
The English summary is being prepared. Showing the original description.
Ultracite 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.
The English summary is being prepared. Showing the original description.
ESLint is the standard linting tool for JavaScript and TypeScript projects. It statically analyzes your code to find problems, enforce coding conventions, and catch bugs before they reach production. ESLint 9 introduced the flat config format, replacing the legacy `.eslintrc` system with a simpler, more composable `eslint.config.js` file. With a rich plugin ecosystem covering React, TypeScript, accessibility, and import ordering, ESLint is the backbone of code quality in modern web development.
The English summary is being prepared. Showing the original description.
Create and refactor Bash scripts following conventions (strict mode, fct_ naming, quoting). Includes shellcheck linting. Use when creating shell scripts, refactoring existing scripts, debugging shell errors, or linting scripts.
The English summary is being prepared. Showing the original description.
Compatibility routing for callers that previously used the holistic-linting orchestrator workflow. Use only when an existing caller explicitly invokes this skill.
The English summary is being prepared. Showing the original description.
Discover and run configured quality gates for requested or changed work, preserve diagnostics as evidence, route failures to the appropriate causal/domain capability, and verify corrections. Use for linting, formatting, type-checking, configured hook checks, or pre-completion quality verification.
The English summary is being prepared. Showing the original description.
Modern Python tooling best practices using uv, ruff, ty, and pytest. Mandates the Trail of Bits Python coding standards for project setup, dependency management, linting, type checking, and testing. Based on patterns from trailofbits/cookiecutter-python.
The English summary is being prepared. Showing the original description.
Use when doing structural code search and rewriting - ast-grep linting, refactoring, multi-language patterns
The English summary is being prepared. Showing the original description.
Detect project linting and validation tools, build an execution pipeline, run all tools to zero errors, and fix issues using an atomic fix protocol. Auto-detects Makefile targets, package.json scripts, Go tools, Python tools, and other common linters. Use when fixing linting errors, running validation pipelines, or ensuring code quality before committing.
The English summary is being prepared. Showing the original description.
ESLint is the standard linting tool for JavaScript and TypeScript projects. It statically analyzes your code to find problems, enforce coding conventions, and catch bugs before they reach production. ESLint 9 introduced the flat config format, replacing the legacy `.eslintrc` system with a simpler, more composable `eslint.config.js` file. With a rich plugin ecosystem covering React, TypeScript, accessibility, and import ordering, ESLint is the backbone of code quality in modern web development.
The English summary is being prepared. Showing the original description.
Linting and code quality workflow for Software Metrics Machine. Covers ESLint 9.x flat config, Prettier formatting, lint-staged (auto-fix on commit), per-workspace configs, TypeScript strict mode, and all lint commands. USE FOR: lint, eslint, prettier, format, code style, linting, lint fix, auto-fix, check style, code quality, lint-staged, typecheck, type-check, tsc noEmit. DO NOT USE FOR: writing tests (use tdd skill), building (use build commands), commit hooks setup.
The English summary is being prepared. Showing the original description.
Code formatting and linting context for the Megahub project. Use when writing or reviewing code in C++ or JavaScript, or when running format/lint checks. Describes tool commands, style conventions, and when to apply them.
The English summary is being prepared. Showing the original description.
Detect project tech stack and configure Claude Code hooks for mechanical enforcement of linting and security rules. Use this skill when a user wants to set up hooks, configure auto-linting, add security guards, or move from advisory CLAUDE.md rules to mechanical enforcement.
The English summary is being prepared. Showing the original description.
Turn a course plan into numbered exercise folders with problem, solution, and explanation variants. Create starter readme files, check naming and links with the project’s linter, and fix structural errors before committing.
Check a Laravel project before merging or deploying. Work through environment settings, code checks, tests and coverage, dependency security, database changes, caches, queues, and scheduled tasks, stopping when a required check fails.
Check a Django application before a pull request or deployment. Review its environment, code quality, database changes, tests, vulnerabilities, and configuration, then produce a phased pass/fail report identifying issues that need fixes.
Check code changes before committing with security scans, tests, linting, and an independent agent review. Compare failures against the previous baseline, then use a separate agent to fix reported problems and repeat verification.
Develop Rust filters for RTK through tests written before implementation. Use real command output as test inputs, check output snapshots and unexpected inputs, verify a minimum reduction target, and complete formatting, linting, and test checks before finishing.