# Repository review worksheet

A free planning and review outline from Brainbaby. This document contains no executed tests or completed changes. Fill in verified facts and leave unknowns visible.

Guide: https://brainbaby.ai/blog/brainbaby-github-integration-chat-with-your-codebase-6vt6

## Source and scope

- Repository:
- Branch:
- Revision:
- Date checked:
- Relevant feature:
- Intended result:
- Behavior that must remain:
- Files or tools unavailable:

Do not include access tokens, private keys, production environment files or customer data the task does not need.

## Reproduce the problem

1. Starting state:
2. Action:
3. Expected result:
4. Actual result:
5. Sanitized error or screenshot reference:

## Evidence from inspected files

| File and function | What was actually read | Finding | Unknowns |
|---|---|---|---|
| | | | |

A file tree or README is not evidence that all source files were inspected. Record the relevant revision and any reading limits.

## Proposed change

- Smallest change that addresses the reproduction:
- Why it addresses that behavior:
- Other callers or workflows affected:
- Newly added dependencies:
- Access or authorization implications:
- Proposed change approved for application: yes / no / not reviewed
- Change actually applied: yes / no
- Diff or pull request reference, if one exists:

## Verification

| Check | Status: passed / failed / not run | Environment and revision | Actual result reference |
|---|---|---|---|
| Original reproduction | not run | | |
| Surrounding workflow | not run | | |
| Relevant automated tests | not run | | |
| Persistence after reload | not run | | |
| Small-screen and keyboard behavior, if relevant | not run | | |
| Authorization and retry behavior, if relevant | not run | | |

A suggested command is not an executed check. Record output from the actual environment. A passed check only establishes the behavior it tested.

## Handoff

- Completed work supported by evidence:
- Failed checks or unresolved questions:
- Checks still needed:
- Next person or action:
- Release readiness: not assessed / blocked by listed work / reviewed for the stated scope

## Bounded investigation prompt

Review the repository at [revision] for [specific behavior]. Start with [relevant files]. Trace the action from input to persistence, cite the files you inspect, and identify unread or unavailable context. Propose the smallest fix for the reproduction. List executed checks separately from recommended checks. Do not claim a test, write or release happened without its result.