Files to inspect
1src/timezone/resolve.ts
2src/invoices/summary.ts
3src/timezone/index.ts
The product
One problem.
Three useful answers.
FixMap narrows the first step, explains its reasoning, and checks the work that followed. It is a map you can inspect—not a promise that the map is always right.
1
You describe the issuein plain English
Users sometimes see invoices in the wrong time zone after daylight saving time changes.
2FixMap finds the few places most likely to matter
Checks to run
1Timezone conversion tests
2DST boundary cases
3Invoice rendering path
Risks to review
1Cached timezone offsets
2External API assumptions
3Off-by-one date handling
01
Before the edit
Plan: find the few places that matter.
FixMap reads the task and the repository together. It ranks likely context files, attaches the evidence behind each score, and routes the nearest tests it can actually reach.
- Ranked source files with reasons
- Workspace-aware test commands
- Risk areas and scan diagnostics
02
When the map surprises you
Explain: ask why a file is missing.
A ranked list explains what it chose. Explain handles the harder question: whether a path ranked lower, fell below the cutoff, was excluded intentionally, or never entered the scan.
- Inspect one path directly
- Distinguish ranking from exclusion
- Surface scan-limit uncertainty
03
After the edit
Verify: compare the plan with the real change.
FixMap checks the saved plan against a git diff. It points out unplanned files, untouched leading context, missing tests, risky areas, and edits in generated or retired locations.
- Plan versus diff
- Advisory findings by default
- Non-zero only for discarded generated edits
What makes the map useful
Grounded signals, not a black box.
FixMap is deterministic. Every ranking point comes from repository evidence that can be inspected and challenged.
Repository connections
Paths, imports, symbols, workspace boundaries, and related tests establish how code fits together.
Calibrated confidence
Confidence is capped when evidence is thin. Vague tasks can return an empty map instead of a plausible guess.
Explicit uncertainty
Scan limits, missing refs, generated files, and remote-fetch behavior appear as diagnostics rather than disappearing.
Safe by construction
FixMap reads and ranks. It does not install dependencies, run scripts, execute tests, or upload local source.
The boundary matters
A starting map, not proof.
FixMap can help an agent search less and review more deliberately. It cannot prove a change is correct, complete, or safe.
That is why every score has reasons, Verify is mostly advisory, and the benchmark page publishes failures alongside hits.
See the evidence