AI Codebase Time-Saver

Analyze this repository before I modify it. I need to add Google OAuth login. First explain the architecture, identify the application entry points, authentication-related files, user/session models, API routes, frontend authentication state, configuration files, and relevant tests. Then tell me exactly which files are likely to change, what existing authentication code I should reuse, what could break, and what tests I should inspect before implementation. Do not modify any files.

CODEBASE INTELLIGENCE REPORT

Repository: example-web-app Analysis Mode: Read-only Requested Change: Google OAuth authentication

1. ARCHITECTURE OVERVIEW

The repository appears to use a frontend application connected to a backend API and persistent user storage.

Primary flow:

Login UI → Auth Client → API Route → Authentication Service → User Store

2. IMPORTANT ENTRY POINTS

Frontend

src/main.* — application bootstrap src/routes/* — route configuration

Backend

server/index.* — server entry server/routes/* — API routes

3. AUTHENTICATION SURFACE

Relevant areas identified:

src/auth/* — frontend authentication logic server/auth/* — server authentication logic server/models/user.* — user persistence src/components/Login.* — login interface

4. LIKELY CHANGE IMPACT

HIGH

src/components/Login.* Existing login interface likely needs an OAuth entry point.

server/auth/* OAuth callback and identity handling may belong here.

MEDIUM

server/models/user.* May require provider/account fields depending on the existing schema.

MEDIUM

Authentication tests should be reviewed before modification.

5. REUSE BEFORE REBUILDING

Existing authentication utilities should be reused where possible rather than creating a parallel authentication flow.

6. POTENTIAL RISKS Existing session handling may conflict with OAuth callbacks. User-account linking may create duplicate accounts. Environment configuration may require new provider credentials. Existing authentication tests may assume password-only login.
7. TESTS TO INSPECT

Prioritize:

Login tests Session tests User creation tests Authentication middleware tests API authorization tests 8. RECOMMENDED IMPLEMENTATION PATH Inspect existing authentication abstraction. Identify current session lifecycle. Determine the repository's existing OAuth/provider pattern if one exists. Extend the existing abstraction rather than creating a second authentication system. Update affected tests. Verify login, callback, session creation, logout, and duplicate-account behavior. CONFIDENCE

Medium

Some implementation details require direct inspection of the relevant authentication modules before changes are made.

No files modified.