convergence-research

To generate a concise research document from your codebase, invoke the research tool against a target repository. It dispatches parallel agents to explore the codebase and produces a compact, fact-only report under 500 lines for fast onboarding.

Question-driven codebase analysis generates targeted questions before researching a repository. It uses ticket-blind exploration and spawns multiple parallel agents to cover different codebase areas, aggregating findings into a concise, audit-ready document.

Yes, you can use parallel agents to analyze a large repository while keeping output manageable. The system dispatches multiple agents concurrently to cover different codebase areas and strictly limits the final aggregated research document to under 500 lines.

The best way to capture codebase insights for fast onboarding is to generate a compact, fact-only research document. This approach includes file paths, signatures, patterns, and recent git history for touched files, ensuring informed decision-making for feature design.

Yes, the codebase research output includes git history context. It records recent git history for touched files within the compact, audit-ready document to preserve context and provide a deeper understanding of codebase evolution.

The generated research document avoids opinions to provide a fact-only report suitable for audit and onboarding. It strictly captures file paths, signatures, patterns, and git history, ensuring objective codebase understanding for informed feature design decisions.