repo-research-analyst

Repository analysis identifies key directories, components, and architectural decisions by examining core documentation like ARCHITECTURE.md and directory patterns. This reveals the project's structural organization, dependency flows, and design rationale to inform code reviews and contributor onboarding.

Key documentation patterns include CONTRIBUTING.md for guidelines, ARCHITECTURE.md for design decisions, CONTEXT.md for project scope, and issue templates for standardized processes. Surfacing these patterns ensures consistent governance and reduces contributor friction across diverse codebases.

Yes. Analyzing repository structure, documentation standards, and governance patterns generates a consolidated map of guidelines and conventions, reducing onboarding time and alignment misalignment for new contributors and teams joining the project.

Audit contribution guidelines by mapping CONTRIBUTING.md, issue templates, and code review patterns documented in the repository. This surfaces existing processes and templates to inform standards and ensure consistent contributor experiences across teams.

Document architectural decisions in dedicated files like ARCHITECTURE.md or CONTEXT.md, supported by clear directory structure and template patterns. Repository analysis identifies these conventions, helping teams apply consistent documentation standards aligned with project governance.