RepoForge

RepoForge is a local-first VS Code extension for preparing repository context packs for coding agents.

It scans a workspace, builds a compact code map, tracks selected files, estimates token usage, summarizes git changes, and writes handoff artifacts to .repoforge/ without calling external AI APIs.

Why it exists

Coding agents are only useful when the handoff is explicit and constrained. RepoForge makes the task, file selection, token budget, and git context visible before anything is sent to a model.

The result is a repeatable input pipeline, not another chat UI.

Screenshot

What it does

• Scan the workspace and build a repository summary.
• Search by path, language, symbol, and import.
• Add the current file or open editors to the context set.
• Manage include modes per file: full, snippet, and codemap.
• Track token budgets and reserved output targets.
• Summarize staged and unstaged git changes.
• Generate Codex, Local Qwen/OpenCode, and Continue handoffs.
• Parse, preview, and apply patches from the clipboard.
• Run validation commands and save the results.
• Save and reload task profiles.

What it is not

• Not a chat UI.
• Not an autonomous agent.
• Not a direct Codex, OpenCode, Continue, or LM Studio integration.
• Not a replacement for repository-specific judgment.

It produces Markdown and JSON artifacts for other tools to consume.

Workflow

1. Run RepoForge: Scan Repo.
2. Open the sidebar.
3. Enter the task.
4. Add files or search for what matters.
5. Review the token budget and adjust include modes.
6. Generate a handoff or copy it into the target agent.
7. If you get a patch back, parse it, preview it, apply it, and run validation.

Modes

Codex

Compact, execution-focused handoff. Best for implementation tasks where code and validation matter more than narrative.

Local Qwen / OpenCode

Longer handoff with more repository context. Best when the target model benefits from broader reasoning context.

Continue

Shorter VS Code-friendly handoff for editor-centric workflows.

Outputs

RepoForge writes its artifacts under .repoforge/:

• last-context.md and last-context.json
• last-handoff.md
• last-patch.diff
• last-patch-preview.md and last-patch-preview.json
• last-validation.md and last-validation.json
• profiles.json
• history/ copies for prior runs

Commands

• RepoForge: Scan Repo
• RepoForge: Open Sidebar
• RepoForge: Generate Codex Pack
• RepoForge: Generate Local Qwen Pack
• RepoForge: Copy Codex Handoff
• RepoForge: Copy Local Qwen/OpenCode Handoff
• RepoForge: Copy Continue Handoff
• RepoForge: Parse Patch From Clipboard
• RepoForge: Preview Patch
• RepoForge: Apply Last Patch
• RepoForge: Run Validation
• RepoForge: Save Task Profile
• RepoForge: Load Task Profile

Development

npm install
npm run compile
npm test

Open the repository in VS Code and press F5 to run the extension host.

Limits

• Token counts are estimates, not model-exact.
• The sidebar is plain HTML, CSS, and JavaScript.
• No network calls or built-in chat interface.
• Patch apply uses git apply and does not stage or commit changes.
• Validation runs only after explicit confirmation.
• Extension-host integration tests are not wired into npm test.