convention-detection

Convention-detection analyzes your repository to identify naming, formatting, and structural patterns across files and languages. It examines config files like ESLint and Prettier, samples representative source files, and generates a structured Markdown and JSON report documenting discovered conventions for your team.

Yes, convention-detection applies across multi-language codebases. It detects naming, layout, and formatting conventions regardless of language, aggregates findings from configuration files and source samples, and outputs unified conventions documentation applicable to your entire repository.

Convention-detection identifies naming conventions, code layout and structure, formatting style, and documentation practices. It reads ESLint, Prettier, and EditorConfig configuration to extract explicit rules, then samples files to discover implicit patterns and report both standardized and emergent conventions.

Convention-detection generates a concise conventions report that documents your team's established patterns and standards. Use the Markdown and JSON output during code reviews to enforce consistency and provide new contributors with explicit guidelines on naming, style, and documentation expectations.

No, convention-detection aggregates conventions automatically by analyzing existing config files like ESLint and EditorConfig alongside representative source files. It requires no manual rule setup—it detects and documents patterns already present in your codebase and tooling.