Skip to main content
Get from zero to a Blitzy pull request. Choose your path based on whether you’re starting fresh or working with an existing codebase.
  1. Go to Settings > Integrations
  2. Click Connect for your provider (GitHub, GitLab, Azure DevOps)
  3. Complete OAuth authorization
  4. Select repositories to enable
Verify: Connection shows “Connected” in Settings > Integrations

​
Create a Project

1

Go to Workspace

2

Create a new project

Click Create new project.
3

Select your path

Choose New Product or Existing Product.
Start with an existing codebase when possible. The Existing Product path gives Blitzy full context of your architecture and patterns, which produces higher-quality output. Use New Product only when you are truly starting from scratch with no existing code to build on.
1

Configure environment

Add build instructions and environment variables in project settings.Optional: Create a blitzy branch for high-activity repos.
2

Write ingestion prompt

Describe your architecture, patterns, and domain terminology.Template: Codebase Ingestion
Templates are not required but highly recommended - they’re structured to give Blitzy the context it needs for thorough output.
3

Review Tech Spec

Blitzy generates a specification of your codebase. Refine as needed.
4

Write generation prompt

Describe the feature or changes to add.Templates: New Feature, Refactor, Bug FixOptional: Add Rules
Rules are reusable directives that enforce quality standards consistently across generations - code style, test coverage, security, and more. Add once to the project instead of repeating the instruction in every prompt.
5

Review Agent Action Plan (AAP)

Blitzy generates a structured plan showing the files it will create/modify and its overall approach before any code is written.Actions: Approve, Discard, or Edit inline.
For most changes, Discard and regenerate with an updated prompt is the recommended approach. Inline edits are best reserved for small, targeted corrections, as larger edits can produce inconsistencies in the generated output.
6

Generate

Blitzy creates code and opens a PR to your target branch.
7

Review Project Guide

Documentation of changes and how they integrate with existing code.
After merging, return to Step 3 for your next generation.

​
Next Steps

Test

Check out the branch and verify functionality

Merge

Follow your review process and merge

Refine

Iterate with follow-up prompts