---
title: "From issue to verified pull request, one context."
description: "Ara reads the issue, reproduces it in an isolated workspace, writes the fix, and verifies it before asking for review. The whole sdlc runs in a single thread of context."
url: "https://ara.so/use-cases/engineering"
section: "Use cases"
---

# From issue to verified pull request, one context.

Ara reads the issue, reproduces it in an isolated workspace, writes the fix, and verifies it before asking for review. The whole sdlc runs in a single thread of context.

## One issue. One context. One pull request.

### Read the issue, reproduce the failure

Ara clones the repo into an isolated workspace and reproduces the bug from the report before it touches a line.

_Reproduce_

### Implement against repo memory

It edits with full context of the codebase and prior runs, so the patch matches your conventions, not generic defaults.

_Implement_

### Verify before it asks for review

Tests, types, and the build run in the same workspace. A red check sends Ara back to step two, not back to you.

_Verify_

### Open a reviewed pull request

You get the diff, a transcript of what it did, and the checks it ran. Then Ara writes back what it learned to repo memory.

_Pull request_

## Context, not autocomplete.

### Grounded in the repo

Every change is written against repo memory built from past runs, so the patch fits the code it edits.

### Verified, not vibes

The fix only ships once the suite, types, and build pass in the same isolated workspace it was written in.

### Review-ready

A scoped diff arrives with the reasoning and the checks that ran, so review takes minutes.

## Point Ara at your backlog.

Connect a repo, hand it an issue, and review a verified pull request instead of writing one.