For coding style guides, the strongest matches are felixge/node-style-guide (This repository provides a JavaScript style guide and accompanying), psf/black (This repository provides a deterministic code formatter and style) and standard/standard (Standard is a popular JavaScript style guide, linter, and). realm/swiftlint and rust-lang/rust-clippy round out the shortlist. Each is ranked by relevance to your query, popularity and recent activity.
Hand-picked coding style guides for popular languages. Compare top open-source repositories by stars and activity to find the best fit.
This project is a JavaScript style guide and Node.js coding standard designed to ensure the creation of consistent, maintainable, and readable code. It serves as a comprehensive reference for naming conventions, formatting, and architectural patterns. The project provides a linting configuration template that allows for the automatic enforcement of these standards. This includes predefined linting presets and a base of rules used to perform logic checks and automatic formatting across a codebase. The guidelines cover a broad range of standardization capabilities, including code and file form
This repository provides a JavaScript style guide and accompanying ESLint configuration templates, making it a solid reference for JavaScript and Node.js best practices, though it lacks the multi-language support requested by the search.
This project is an uncompromising, deterministic code formatter for Python. It functions by parsing source code into an abstract syntax tree and regenerating it according to a rigid, opinionated set of style rules. By automating the formatting process, it eliminates manual style debates and configuration overhead, ensuring that code remains consistent across entire projects regardless of the original input. The tool distinguishes itself through its focus on speed and seamless integration into development workflows. It utilizes content-based file caching and parallel processing to maintain hig
This repository provides a deterministic code formatter and style enforcer for Python, but its single-language focus means it lacks the multi-language support requested.
Standard is a suite of static analysis tools for JavaScript, comprising a linter, formatter, and a predefined style guide. It functions as a static code analyzer that scans source code for style violations and potential errors without executing the program. The project provides an automatic code fixer that rewrites source code to resolve formatting issues and enforce syntax consistency. It implements a standardized set of rules for JavaScript formatting and syntax to ensure a uniform appearance across different projects. The system covers a wide range of static analysis capabilities, includi
Standard is a popular JavaScript style guide, linter, and formatter that enforces predefined coding conventions, though its lack of multi-language support keeps it narrower than a universal rules collection.
SwiftLint is a static analysis tool and code formatter designed to enforce consistent coding styles and identify semantic issues within Swift source code. It functions as a command-line utility that evaluates code against established conventions to ensure uniform structure and architectural standards across a project. The tool distinguishes itself through a custom linting engine that leverages compiler-integrated syntax analysis to perform deep inspections of code structure. Beyond simple pattern matching, it supports automated source code transformation to correct formatting violations and r
SwiftLint is a dedicated linter and code formatter for Swift that enforces style guides and best practices, though its scope is limited to a single language rather than multi-language support.
This project is a static analysis linter, code quality tool, and language auditor for Rust. It functions as an automated refactoring system designed to identify common mistakes and suggest idiomatic improvements for Rust source code. The tool identifies non-idiomatic patterns, performance bottlenecks, and code smells to improve the overall correctness and quality of the code. It specifically audits memory safety by flagging suspicious use of unsafe blocks and pointer manipulations and detects inefficient operations to optimize execution speed. The analysis surface covers coding style enforce
This project is a dedicated static analysis linter and code quality tool for Rust, capturing the linting and style-enforcement aspects of the search while remaining limited to a single language rather than multi-language support.
RuboCop is a static code analyzer and linter for Ruby. It functions as a static analysis tool designed to detect potential bugs, identify style violations, and improve overall code quality in Ruby projects. The project provides an automated code formatter that rewrites source code to align with established community standards. It also implements a language server protocol to surface linting and formatting errors directly within text editors. Its capabilities cover automated code linting and the analysis of Ruby code style to ensure consistency across a project. These functions are driven by
RuboCop is a robust static code analyzer and formatter for enforcing style guides, though its language support is strictly limited to Ruby rather than multiple programming languages.
This project provides a set of software architecture guidelines, Lisp coding standards, and functional programming patterns for Clojure development. It establishes best practices for implementing declarative logic and managing shared state through the use of persistent data structures and atomic references. The guide covers standards for documenting public APIs and organizing project directories to ensure portable library distribution. It details the application of consistent formatting and naming rules to improve source code readability and team collaboration. The scope extends to idiomatic
This repository provides a comprehensive collection of community best practices and style guidelines for Clojure development, though it functions as a human-readable reference rather than an automated linter or CI tool.
This project is a static analysis tool and linter designed to improve the quality, reliability, and portability of shell scripts. By performing deep structural analysis, it identifies common programming pitfalls, syntax errors, and security vulnerabilities before scripts are executed. It functions as an automated code reviewer that enforces best practices and helps developers maintain consistent, robust code across different operating environments. The tool distinguishes itself through its dialect-aware grammar resolution, which adapts its parsing logic based on the specific shell interpreter
ShellCheck is a dedicated static analysis linter that enforces shell script best practices and flags code quality issues, serving as a robust language-specific tool for this search even though it lacks multi-language support.
The CppCoreGuidelines is a comprehensive software engineering standard that provides a curated framework of coding conventions and design principles for C++. It serves as an authoritative guide for writing safe, efficient, and maintainable code by establishing high-level architectural patterns and organizational principles for large-scale projects. The guidelines emphasize the use of a strong, static type system to ensure memory safety and enforce consistent resource management patterns. The project distinguishes itself by promoting the zero-overhead abstraction principle, ensuring that high-
This repository provides an authoritative, comprehensive collection of C++ coding style guidelines and best practices, though it focuses purely on documentation rather than active linters or automated configuration files.
This project is a collection of Swift coding standards and static analysis rules designed to ensure consistency across Swift projects. It provides a defined set of naming conventions and structural guidelines to maintain a shared style for teams. The repository centers on a SwiftLint configuration used to automate the detection and correction of style violations in source code. This configuration enables automated style enforcement, ensuring that code adheres to organizational standards without requiring manual review. The guidelines cover the standardization of code formatting, naming, and
This repository provides a dedicated Swift coding style guide alongside a pre-configured static analysis setup for automated enforcement, though its multi-language support is limited to Swift.
This project is a static analysis tool and linter for Elixir designed to enforce a unified visual structure across codebases. It serves as a specification for code formatting, naming conventions, and documentation standards. The tool provides a standardized system for casing and prefixes used in files, functions, and variables. It also establishes guidelines for formatting module and function descriptions to ensure consistent technical documentation. The project covers a broad range of code quality areas, including the organization of module layouts, the implementation of commenting patterns
This repository provides a concrete style guide and static analysis linter specifically for Elixir, making it a good fit for enforcing best practices even though it is limited to a single language rather than multi-language support.
This project is a comprehensive set of standards for the Swift ecosystem, providing a code style guide, API design standards, and a memory management guide. It establishes standardized naming and formatting rules to ensure consistent and maintainable source code. The project includes a linting configuration used by automated tools to detect and enforce syntax patterns. These rules are designed to standardize code style and can be integrated into build phases to block commits with formatting errors. The guidelines cover a broad range of development capabilities, including the use of access mo
This repository provides a comprehensive Swift style guide complete with linting configurations to enforce code quality and best practices, though it is limited to the Swift ecosystem rather than offering multi-language support.
JSHint is a JavaScript static analysis tool and linter designed to detect errors and enforce coding standards. It functions as a syntax validator that scans source code to identify potential logic problems and programming mistakes before the code is executed. The tool provides a command line interface for analyzing files and directories. It supports the export of analysis results into standardized formats such as Checkstyle for integration with external build tools. Analysis is managed through a system of linting rule management and environment global configuration. This includes the ability
JSHint is a static analysis tool and linter that enforces coding standards and detects errors specifically for JavaScript, making it a solid choice though limited by its single-language scope rather than multi-language support.
This project provides a comprehensive framework for standardizing CSS architecture and development practices in large-scale web applications. It establishes a structured approach to managing design patterns, ensuring that stylesheets remain maintainable, scalable, and consistent across complex codebases. The methodology centers on the use of block-element-modifier naming conventions to organize user interface components into independent, reusable units. By enforcing flat selector specificity and namespace-based scoping, the framework prevents naming collisions and unintended style overrides.
This repository provides a comprehensive CSS style guide and architectural framework for standardizing frontend development practices, though its scope is limited to stylesheets rather than multi-language support.
Pylint is a static code analyzer for Python that scans source code for errors, coding standard violations, code smells, and type-related issues without executing the program. It functions as a plugin-based linter framework, allowing users to extend its analysis capabilities with custom or third-party checks for project-specific rules and framework support. The tool also includes a duplicate code detector that identifies identical or near-identical code blocks across a project to help reduce redundancy. Beyond its core linting functionality, Pylint can generate UML class and package diagrams f
Pylint is a static code analyzer for Python that enforces coding standards and detects errors, though it is limited to Python rather than offering multi-language support.
This project is a software engineering style guide and a curated collection of architectural patterns and coding standards. It provides a multi-language coding standard to ensure maintainable software across Ruby, Python, JavaScript, and Swift. The project establishes a development workflow specification for version control, continuous integration, and peer review to maintain a linear project history. It also includes a web accessibility framework based on ARIA and WCAG standards, using design tokens and semantic HTML patterns to build inclusive interfaces. The guides cover a broad range of
Thoughtbot/guides collects multi-language coding standards and architectural patterns, matching the requirement for a reference repository of best practices even though it lacks automated linters or editor plugins.
This project provides a comprehensive set of coding standards and style guidelines for JavaScript development. It covers fundamental language syntax, formatting conventions, and best practices for managing variables, functions, objects, and modern language features. The documentation serves as a reference for maintaining consistent code quality across projects. In addition to general language standards, the guide includes specific conventions for building and organizing user interface components. These guidelines address structural patterns, component lifecycle management, and stylistic rules
This repository provides a widely adopted reference style guide and shareable ESLint configuration for JavaScript, fitting the core request for community-driven best practices and linting rules even though it focuses on a single language rather than multi-language support.
This project is a PHP clean code guide and software architecture reference. It provides a set of standards, naming conventions, and design patterns intended to improve the long-term maintainability and readability of PHP codebases. The guide emphasizes a structured approach to refactoring and system design, focusing on the application of SOLID principles to reduce coupling and increase extensibility. It advocates for object-oriented design through the use of composition over inheritance, the use of final classes to prevent unexpected overrides, and the implementation of strict type declaratio
This repository provides a dedicated PHP coding style guide and software architecture reference, though it functions as a documentation guide rather than an automated linter or CI tool.
This project provides a set of Android development guidelines, architecture standards, and a coding style guide. It establishes uniform formatting and implementation rules to ensure code consistency and maintainability for applications built on the Android platform. The project includes a standardized project structure template that defines consistent folder hierarchies and file layouts. These standards are designed to maintain a predictable development experience across multiple workstreams. The guidelines cover architectural patterns including layer-based separation of business logic and p
This repository provides a comprehensive collection of code style guides and architectural best practices specifically tailored for Android development, though its multi-language support is limited.
This project provides a collection of coding standard specifications, style guides, and configuration assets used to define automated rules for static code analysis in Ruby. It serves as a centralized set of RuboCop configurations and static analysis rules to ensure consistent syntax and idiomatic usage across a codebase. The project establishes a comprehensive Ruby style guide that defines naming conventions, indentation, and structural requirements. It utilizes a pluggable linting engine to enforce these standards through a defined set of patterns and constraints. The capability surface co
This project provides a comprehensive Ruby coding style guide and configuration assets for static code analysis, fitting the category well despite being limited to a single language rather than multi-language support.
Bulletproof React is an architectural guide and project boilerplate designed to standardize the development of large-scale, maintainable frontend applications. It provides a set of structural principles and organizational strategies that enforce a strict separation of concerns, ensuring that codebases remain manageable as they grow in complexity over time. The project distinguishes itself by promoting a modular design that groups related logic, components, and services into dedicated feature folders. It utilizes a composition-based approach to build user interfaces and implements a dependency
Bulletproof React is a comprehensive architectural guide and boilerplate that defines best practices and project structure for React applications, though it focuses on architectural patterns rather than traditional multi-language linting and formatting rules.
This project establishes a collection of interoperability standards for the PHP ecosystem. It defines common technical specifications to ensure that separate software projects and libraries can work together without compatibility issues. The standards cover a variety of core domains, including specifications for class autoloading through namespace-to-path mapping, shared coding style guides for codebase uniformity, and common component interfaces for services such as logging and caching. It also defines shared specifications for network communication to ensure consistent interactions between
This repository defines official PHP coding style guides and interoperability standards, though it focuses on human-readable specification documents rather than automated linters or multi-language collections.
This project is a curated collection of best practices, coding standards, and style guidelines for writing C++ source code. It serves as a software engineering resource focused on improving code safety, maintainability, and performance. The resource covers multiple domains of C++ development, including safety engineering to reduce bugs and memory errors, as well as code optimization for increased efficiency. It provides a set of collaborative guidelines for consistent code formatting and structural patterns across projects.
This repository provides a comprehensive collection of community best practices and coding standards for C++, serving as a valuable reference guide for software engineers despite lacking automated linters or CI integration tools.
Style guides for Google-originated open-source projects
This repository genuinely provides official coding style guides and best practices for various languages, though it focuses on documentation rather than automated linters and automated formatting tools.
This project is a community-driven Ruby coding style guide and static analysis standard. It provides a collection of agreed-upon rules for syntax, naming conventions, and structural guidelines to ensure uniform code appearance and maintainability across Ruby projects. The project serves as both a human-readable documentation resource for developers and a machine-readable RuboCop configuration specification. This allows natural language style guidelines to be mapped directly to automated linting rules. The system covers Ruby code standardization, style enforcement, and project governance thro
This repository provides a comprehensive community-driven style guide and static analysis standard for Ruby, though it focuses exclusively on a single language rather than multi-language support.
This project is a collection of community-driven coding standards and best practices for developing maintainable Ruby on Rails applications. It serves as a style guide, architecture reference, and development guide to ensure consistency across a codebase. The guide provides technical recommendations for establishing naming conventions and architectural patterns. It specifically focuses on organizing models, controllers, and views to separate business logic from data persistence and user interface presentation. The documentation covers a broad range of capabilities, including RESTful API desi
This repository provides a community-driven collection of coding standards and best practices specifically for Ruby on Rails, fitting the target category though it is limited to a single language and lacks automated linters or CI integration.
The project establishes consistent naming conventions, readability standards, and structural best practices across large PySpark data transformation codebases. It provides architectural patterns and performance recommendations designed to prevent common data transformation pitfalls in distributed systems, alongside recommendations for organizing code logic and structuring expressions within large-scale data processing codebases. The guidelines cover performance optimization through the replacement of custom user-defined functions with native operations, big data join safety by validating key
This repository genuinely provides a style guide and best practices for PySpark development, though its scope is focused strictly on a single language and framework rather than offering multi-language support or automated tooling.
The repository contains a curated collection of coding conventions, architectural patterns, and best practices designed for developing component-based web applications using Angular and TypeScript. It functions as an architecture manual establishing consistent patterns across development teams, covering application structure, component design, and code quality enforcement. The guidelines define domain-driven file organization and module encapsulation strategies that group project assets into bounded contexts with dedicated root facades to keep large codebases manageable and shorten import pat
This repository provides a community-driven collection of best practices and style guidelines, though it focuses specifically on Angular development rather than multi-language support.
Style Guide is an open-source JavaScript project maintained by Vercel that provides standardized configuration rules and shared settings for development environments. It supplies unified linting rules, formatting guidelines, and tooling configurations to maintain consistency across codebase repositories. The repository includes packages and preset configurations designed for integration into JavaScript and TypeScript project workflows.
This repository genuinely is a collection of coding style guides and best practices from an engineering team, though it is focused primarily on JavaScript and TypeScript rather than multi-language support.
js-the-right-way is a JavaScript best practices guide and coding standards reference designed to provide a curated collection of industry materials for writing maintainable code. It serves as a web development education resource, offering organized documentation on modern JavaScript patterns and idioms. The project is structured as a markdown-based documentation site, where guides written in lightweight markup are rendered as static pages. It utilizes a curated network of hyperlinks to connect internal documentation with external industry standards.
This repository provides a curated collection of JavaScript best practices and coding standards, serving as a reference guide for developers although it lacks automated tools or linters.
This repository provides a set of community coding style rules and best practices specifically for Scala, making it a relevant reference guide despite lacking automated tooling or multi-language support.
This project is a version control style guide providing standardized rules for commit messages, branch naming, and history management. It serves as a comprehensive framework for maintaining a consistent and readable project history through a set of defined guidelines and workflow documentation. The guide emphasizes a linear history branching model, utilizing rebasing and squashing techniques to maintain a straight timeline of commits. It specifies a structured commit layout using imperative language and a kebab-case naming convention for branches to ensure organizational clarity across teams.
This repository provides a standardized guide for Git workflows, commit messages, and branch naming, making it a relevant stylistic reference despite lacking automated linters or code formatting rules.
A style guide for Haskell code.
This repository provides a community style guide for Haskell code, fitting the category of best practices collection though it focuses exclusively on a single language rather than multi-language support.
This project is a JavaScript style guide and a set of coding standards designed to ensure codebase consistency. It provides a collection of best practices for writing maintainable and idiomatic code, focusing on variable naming, type checking, and execution context. The project serves as a static analysis guide, offering frameworks and guidelines for using linters and automated tools to identify bugs and verify code correctness before deployment. It establishes standards for formatting, syntax, and variable declarations to standardize code style across a project. The scope of the project cov
This repository provides a JavaScript coding style guide and best practices collection, though it is limited to JavaScript rather than offering the multi-language support requested.
LinkedIn's Official Swift Style Guide
This repository provides LinkedIn's official style guide for Swift, acting as a direct reference for coding standards even though it lacks automated linters or multi-language support.
Opinionated jQuery Style Guide for teams.
This repository provides a single-language style guide for jQuery, making it a relevant community resource though it lacks the multi-language support and automated tooling requested.
Style guide for Android by Xmartlabs
This repository genuinely provides an Android coding style guide, though its scope is limited to a single platform rather than multi-language support.
Style Guide for the Elixir language, implemented by Credo
This repository provides a community-driven style guide specifically for Elixir, making it a useful reference for best practices though it focuses on a single language rather than multiple ones.
😎 A style guide that helps you write better, performant, structured, scalable, and maintainable HTML.
This repository provides a comprehensive HTML style guide and best practices collection to help write scalable and maintainable markup, though it focuses on a single language and lacks automated linters.
This project is a community-driven style guide that defines standards for formatting and structuring Ruby code. It serves as a collection of language conventions and best practices intended to ensure that Ruby applications are written idiomatically and maintainably. The guide functions as a static analysis standard, providing a reference that automated linting tools use to enforce uniform coding patterns and structural rules. By mapping written guidelines to these automated configurations, it establishes a shared source of truth for code consistency. The scope of the project covers Ruby code
This repository is a community-driven style guide and standard reference for Ruby coding conventions, directly serving the visitor's need for best practices despite focusing exclusively on a single language rather than multiple.
A community-driven Emacs Lisp style guide
This repository provides a community-driven Emacs Lisp style guide and best practices collection, though it focuses narrowly on a single language and lacks automated linters.
| 仓库 | Star 数 | 语言 | 许可证 | 最后推送 |
|---|---|---|---|---|
| felixge/node-style-guide | 5K | JavaScript | — | |
| psf/black | 41.6K | Python | MIT | |
| standard/standard | 29.4K | JavaScript | MIT | |
| realm/swiftlint | 19.5K | Swift | mit | |
| rust-lang/rust-clippy | 13.3K | Rust | Apache-2.0 | |
| bbatsov/rubocop | 12.9K | Ruby | MIT | |
| bbatsov/clojure-style-guide | 4.1K | — | — | |
| koalaman/shellcheck | 39.6K | Haskell | GPL-3.0 | |
| isocpp/cppcoreguidelines | 45.1K | CSS | NOASSERTION | |
| raywenderlich/swift-style-guide | 13.2K | — | NOASSERTION |