Enforce file and directory naming conventions via .ls-lint.yml configuration.
npx skills add https://github.com/PaulRBerg/agent-skills --skill ls-lint
Please help me install this Agent Skill. Skill: ls-lint Source: https://github.com/PaulRBerg/agent-skills/tree/main/skills/ls-lint Command: npx skills add https://github.com/PaulRBerg/agent-skills --skill ls-lint
This Skill helps teams enforce consistent file and directory naming across projects, reducing ambiguity and improving tooling reliability.
Install the tool via npm: npm install -D @ls-lint/ls-lint Run with the default configuration: npx @ls-lint/ls-lint Optional: install via Homebrew: brew install ls-lint Create a minimal config file (.ls-lint.yml) to define your naming rules.
High-intent search queries and answers about installing and using this skill.
Enforce consistent file and directory naming by installing ls-lint (npm install -D @ls-lint/ls-lint), creating a .ls-lint.yml configuration file with your naming rules, and running npx @ls-lint/ls-lint to validate all files and directories against those conventions.
ls-lint supports multiple naming conventions including lowercase, kebab-case, camelCase, PascalCase, snake_case, and SCREAMING_SNAKE_CASE, allowing you to define separate rules for directories and files in your configuration.
Yes, ls-lint is suitable for CI checks. Install it via npm, Homebrew, or direct binary download, then run it as part of your pipeline to catch naming convention violations early before code is merged.
Install ls-lint with npm install -D @ls-lint/ls-lint, run npx @ls-lint/ls-lint with the default configuration to see what's enforced, then customize your .ls-lint.yml file to match your team's naming standards.
Each project needs its own .ls-lint.yml configuration file to define naming rules for directories and files. ls-lint provides a straightforward configuration format, so setup is minimal even for large codebases.
Consistent naming reduces ambiguity, improves tooling reliability, and makes onboarding easier for new team members. It ensures readability and compatibility across large projects where multiple developers contribute.
Maj3D10Centralize .NET build settings and package versions with Directory.Build.props and Directory.Packages.props.
pascallammersConfigure ESLint, Prettier, and Husky to enforce coding standards.
MolcajeteAIConfigure Husky and lint-staged pre-commit hooks for automated code quality checks.
pax-kEnforce and document architecture boundaries using dependency-cruiser, ESLint, import-linter, and custom scripts.
