skills.rest
organvm-i-theoria
organvm-i-theoriaOFFICIAL
Explore all skills by this author →
GitHub

coding-standards-enforcer

Configures ESLint, Prettier, and pre-commit hooks to enforce consistent code style.

Updated May 16, 2026
Search Tags:#code quality#typescript#linting#code style#eslint#prettier#pre-commit hooks
One-click install
npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill coding-standards-enforcer-organvm-i-theoria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coding-standards-enforcer
Source: https://github.com/organvm-i-theoria/_agent-ontology/tree/main/.agents/skills/coding-standards-enforcer
Command: npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill coding-standards-enforcer-organvm-i-theoria

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires eslint, prettier, husky, lint-staged, and includes references (resource) components.

What problem does it solve? Codebases drift into inconsistent formatting, naming, and structure when teams lack automated enforcement, leading to noisy diffs, review friction, and style debates. This Skill provides ready-to-use linter, formatter, and Git hook configurations that enforce standards automatically. ## Core Features & Use Cases - Linter and Formatter Setup: Provides ESLint rules (TypeScript, React, complexity limits) and Prettier configuration for automated style enforcement. - Pre-commit Automation: Configures husky and lint-staged so staged files are linted and formatted before every commit. - Naming and Structure Standards: Includes a reference style guide covering naming conventions, error handling, comments, testing patterns, and commit message formats. - Use Case: When bootstrapping a new TypeScript project, apply this Skill to generate the ESLint config, Prettier settings, and pre-commit hooks so every contributor's code is checked automatically from the first commit. ## Quick Start Set up ESLint, Prettier, and husky pre-commit hooks for my TypeScript project using the coding standards enforcer.

Frequently Asked Questions about coding-standards-enforcer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up ESLint and Prettier for a TypeScript project?▼

Extend eslint:recommended with @typescript-eslint/recommended and prettier in your ESLint config, then add a Prettier config defining semicolons, quotes, and print width. The Skill provides complete working configurations for both tools.

How to run linting automatically before every git commit?▼

Install husky and lint-staged as dev dependencies, run npx husky install, then add a pre-commit hook running npx lint-staged. Configure lint-staged in package.json to run eslint --fix and prettier --write on staged files.

What naming conventions should I use in TypeScript?▼

Use PascalCase for classes, interfaces, and types; camelCase for functions and variables; SCREAMING_SNAKE_CASE for constants; and kebab-case for files. Boolean variables and functions should use is, has, can, or should prefixes.

Does lint-staged work with files other than TypeScript?▼

Yes, lint-staged accepts glob patterns for any file type. The provided configuration runs ESLint and Prettier on .ts and .tsx files, and Prettier alone on .json and .md files, and you can add more patterns.

What are the limits of automated linting for code quality?▼

Linters enforce syntax, formatting, and simple complexity rules but cannot judge architectural decisions, business logic correctness, or readability trade-offs. Combine automated checks with code review and testing for full quality coverage.

Related Skills

Explore More Software Engineering Skills→
diriendirien
19

lint-fix

Detect linting and validation failures and fix them atomically across project toolchains.

Community
Advanced
WellApp-aiWellApp-ai
341

code-review

Detect hard-rule violations and quality issues in JavaScript/TypeScript code changes.

Official
Intermediate
vm0-aivm0-ai
1.1k

commit

Run format, lint, type-check, and test steps before Git commits.

Official
Intermediate
jonlwowski012jonlwowski012
16

code-formatting

Format code across projects using detected configuration files and language-specific formatters.

Community
Intermediate