project-conventions

To discover project conventions, scan configuration files like eslint, prettier, tsconfig.json, and editorconfig alongside repository structures. This surfaces implicit patterns and generates a practical checklist to align code across modules.

Inconsistent naming and structure patterns occur when implicit conventions drift across modules. Scanning configuration files and repository structures surfaces these patterns, providing a structured discovery process to enforce uniform practices and reduce drift.

Yes, this targets codebases across multiple programming languages by scanning common configuration files and documentation. It discovers and applies conventions for naming, structure, and guidelines regardless of the specific language used.

The best way to align contribution guidelines is through guided adoption, which generates actionable steps to integrate discovered conventions into existing projects. This enforces discovered patterns and structured checklists to ensure uniformity across teams.

Codebase convention discovery relies on scanning common config files, directory structures, and documentation. If explicit configurations are missing, the process uses repository structure and documentation to surface implicit conventions and provide actionable guidance.