bbatsov/clojure-style-guide

A community coding style guide for the Clojure programming language

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 24 minutes ago
Type:Documentation / SpecificationCategory(s):Cheatsheets, Checklists & Best PracticesLearning & Resources
Added to GitGenius on September 16th, 2026
Created on January 3rd, 2013
Open Issues & Pull Requests: 46 (+0)
GitHub issues: Enabled
Number of forks: 282
Total Stargazers: 4,100 (+0)
Total Subscribers: 136 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.6 hours
Mean response time: 50.6 days
90th percentile: 353.9 days
Tracked items: 7

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 1,462 days
Stale 30+ days: 3
Stale 90+ days: 3

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 2
Events in 7 days: 4

Top labels

  • enhancement (1)

Most active issues this week

Detailed Description

Clojure Style Guide is a community coding style guide for the Clojure programming language.

The guide addresses the need for consistent code conventions across Clojure projects by establishing shared standards for formatting, naming, and structural patterns. It works by documenting recommended practices for indentation, whitespace, naming conventions, and idiomatic Clojure patterns, providing developers with a reference to align their code with community expectations.

Developers working on Clojure projects should adopt this guide if they want their code to follow established community conventions and improve readability across teams. It suits any Clojure project, from small utilities to large applications, and is particularly valuable for teams that want to enforce consistent style without debating standards from scratch. The guide serves as a foundation that can be extended with project-specific rules while maintaining alignment with broader Clojure practices.

The project maintains an active engagement with the Clojure community through ongoing refinement of recommendations. Updates reflect evolving best practices and incorporate feedback from practitioners using the guide in real-world codebases. The guide remains a living document that balances stability in core principles with responsiveness to how the language and its ecosystem develop.