Ticket to PR · A traceable workflow
Ticket-to-PR connects a software assignment to repository changes and a review handover. Anvil Coder plans implementation, coordinates coding agents and records check results. The hosted service produces a draft pull request for your team to assess before merging.
Describe behaviour, boundaries and acceptance criteria in the internal board or a connected tracker. Connect the repository and define your project rules.
The task is divided into small work units with dependencies. Review unresolved assumptions and configure the approvals your project needs.
Agents produce commits. Configured checks report findings; build and test execution require an available toolchain.
Open the pull request in your Git host. Inspect the diff, acceptance criteria and executed checks before deciding whether to merge.
Illustrative task · not a benchmark
A title leaves many decisions open. These acceptance criteria make the assignment more concrete for implementation and review:
The handover should bring implementation, test changes and check results together. Tests that did not run and unresolved assumptions belong in your review decision.
Provide the affected feature, intended behaviour, relevant documentation and changes explicitly outside scope. A small, bounded ticket makes the first result easier to assess.
For larger work, start with a specification and curated epics. Generating tickets prepares work; it does not itself start a coding run.
Connect three perspectives: what was requested, what changed and what was checked. The commit history helps you follow implementation. The run report records executed checks and their results.
A passing check covers only what it actually examines. Your team still assesses domain correctness, appropriate permissions and unexpected effects in the concrete diff.