Documentation
Getting started.
A short guide to a short process.
Up and running.
- Paste a ticket. The title is usually enough.
- Attach the Figma link. We’ll assume the empty states.
- Approve the 1,400-line pull request marked “minor cleanup.”
Sensible defaults.
AlmostRight arrives preconfigured. Most settings are not adjustable.
ask_questions: false assumptions: unlimited memory_of_decisions: none confidence: 1.0 review: optional
From ticket to pull request.
The agent reads your ticket, locates the relevant code, and implements its interpretation. Tests are updated to reflect the result.
A note on context
Comments beginning “for historical reasons” are treated as candidates for removal.
Common questions.
How do I tell it why?
That field is not currently available. Atono takes a different approach ↗
Can I provide more context?
You can put it in the ticket. The conversation where the decision was made won’t come along on its own.
What if the result is wrong?
Create a new ticket. Label it “follow-up” so the original still counts as done.
Troubleshooting.
The output is wrong.
The ticket was wrong.
The ticket was not wrong.
Then it was incomplete. Same category.
It removed something we needed.
The code did not explain why it was there. Add a comment. We have a separate process for not reading those.
The tests were passing before.
They are passing now.
How do I roll back?
Create a ticket describing the previous behaviour. The agent will decide what you meant.
From Atono
There’s usually a reason.
Keep the decisions behind the work close enough for your team—and its AI—to find them.