How insaneodyssey26/what-the-code works
Project type and purpose
• This is a VS Code extension written in TypeScript.
• It provides three main features:
• Natural-language Q&A on your code via a Gemini AI API
• Dead-code discovery and removal (unused imports, functions, variables)
• Snapshot/restore of files before modifications
File structure
• Top-level:
• package.json / tsconfig.json / eslint.config.mjs – project config & dependencies
• .vscode / .vscodeignore – VS Code packaging settings
• src/: all business logic, e.g.:
• extension.ts – activation/deactivation, command registration
• *Providers (aiProviders, mainActionsProvider, resultsDisplay, etc.) – modules responsible for VS Code UI webviews and tree views
• codeCollector.ts, getProjectFiles.ts – scanning project files
• analyzeDeadCode.ts, deadCodeFinder.ts, deadCodeRemover.ts – dead-code analysis & edits
• snapshotProvider.ts – save/restore file state
• types.ts, uiPresets.ts – shared types, UI styling presets
README for additional insights
• Confirms use of Gemini API for Q&A
• Describes three distinct features (chat, dead-code, snapshots)
• Usage via a command (Ctrl+Shift+Alt+K) and a sidebar
1. VS Code Host
• Command Palette
• Sidebar / Webview Container
• Editor / Text Documents
2. Extension Core (our code)
• Activation Module (extension.ts)
• UI Controllers (searchInput, resultsDisplay, mainActionsProvider)
• Services:
• AIService (aiProviders.ts)
• DeadCodeService (analyzeDeadCode, deadCodeFinder, deadCodeRemover)
• SnapshotService (snapshotProvider)
• FileSystemService (codeCollector, getProjectFiles)
3. External Gemini API (Google AI Studio)
• User triggers command in VS Code → Extension Activation Module
• Activation Module → registers Command Handlers & Tree/Webview Providers
• UI Controllers render input form / result tree → user enters query or clicks “Find Dead Code”
• On query: UI Controller → AIService → Gemini API → AIService receives response → UI Controller updates Webview
• On “Find Dead Code”: UI Controller → FileSystemService scans files → DeadCodeService analyzes → DeadCodeService returns suggestions → UI Controller shows code actions → user applies fix → DeadCodeService applies edits via VS Code API
• On any operation: SnapshotService optionally saves or restores file state
c. Architectural patterns & design principles
• Modular “Provider” pattern to separate UI from business logic
• Single Responsibility: each service (AI, DeadCode, Snapshot, FileSystem) encapsulates its own domain
• Event-driven flow: user actions → commands → providers → services → VS Code editor
d. Key technologies, frameworks, libraries
• TypeScript & Node.js
• VS Code Extension API
• Google Gemini REST API
• ESLint config for linting