“linting and formatting”

Linting and formatting for Megatron-LM.

Code style and quality rules for Megatron Bridge — ruff configuration, naming conventions, type hints, mypy rules, docstrings, copyright headers, logging, and…

When a repo has inconsistent style or no linter or formatter.

Reference for poly, the single-binary multi-language linter and formatter — per-language engines, the lint/fmt commands, poly.toml configuration, severity…

Installs a PostToolUse hook that runs the project's linter and formatter on every file Claude Code or one of its subagents writes or edits, and speaks up only…

Install and configure JavaScript/TypeScript typechecking, linting, formatting, Git pre-commit hooks, and GitHub Actions CI checks.

Run formatting and linting via Makefile (make format, make lint).

AGENTS.md from aio-libs/aiohttp: 72 lines covering Branching, Build, Test, Lint & Format and more.

Four-gate quality model - build, lint, format, test - that must all pass before any commit.

Run full lint + format + test + frontend build.

AGENTS.md from NangoHQ/nango: 43 lines covering Linting & formatting, Product analytics, Running Nango locally, Running the webapp dev server and more.

Run local QA including formatting, linting, and testing for the repository.

Run formatting, lint, typecheck, and tests for this repo; use when validating changes or investigating CI failures.

AGENTS.md from tsparticles/tsparticles: 192 lines covering Quick Commands, Lint / Format / Commit hooks, Tests, Build & Bundles and more.

Fix lint, formatting, and prose issues in markdown files using Prettier and Vale.

Run linting and formatting.

Pare Lint ג€” Structured linting and formatting (ESLint, Prettier, Biome, Oxlint) as typed JSON.

Formatting and style guidance for CSS/stylesheet code: organization, naming, and linting.

When running, packaging, linting, formatting, or type-checking Python — use uv, Ruff, and ty with changes scoped to touched code.

Run all code quality checks for the current project including linting, formatting, and type checking.

Use when a pull request has failing CI checks — lint, format, type-check, test, or build failures — that need to be diagnosed and fixed to get CI green.

Common Taskfile commands across xberg-io repos — setup, build, test, lint, format, coverage, and bench.

Go formatting skill for gofmt, goimports, and IDE configuration.

Standards for analysis, linting, formatting, and automation.