Why agent-written code is safe to merge
Every pull request is read by review agents following your repository's own review skills. They send it back until it comes back clean, inside a budget set by the ticket's size.
Your review skills
Review skills live in your repository, in .tick-it/skills: one for security, one for docs, one for whatever your team cares about. Each says when it runs and what counts as blocking.
Blocking and optional findings
A blocking finding starts a fix round: a session fixes it and the agents review again, saying whether each earlier finding is fixed, still open or gone. Optional findings don't hold the ticket back.
Limits
Review stops at a clean round, at the size's round limit or at its review budget. A person can let one ticket's reviews carry on until a round comes back clean.
Nothing a reviewer noticed is lost
Proposals
Optional findings are grouped into proposed tickets with a size, epic and acceptance checks. Create or dismiss them one at a time or in one go.
Review trends
Findings, review rounds and changed lines of the tickets that went Done each week, for everyone in the repository.
Before and after pictures
A change to what people see carries before and after pictures, posted on its pull request by the GitHub App.