Ticket to PR · A Tessl Factory loop

From ticket to PR, built around your team’s standards

Turn tickets into pull requests, guided by your team’s engineering standards. Tessl implements the change and works through review feedback, so your team can focus on shipping.

Talk to our team Automate tickets to PR

JiraComing soon

Assign a Linear issue or label a GitHub issue.

Tessl works on it.

Review and approve the pull request.

LinearTES-187

Todo

Add date picker to report filters

Filter reports by date range. Match our design system styles.

YouAssignee

TesslDelegate

TesslWaiting

Implement
Code review
Remediation
Re-review

Pull request#2843

Add date picker to report filters

Code Review

Verifiers

Snyk: no known vulnerabilities

Ready for your approval

From ticket to review to merge

Once your factory is configured, assigning a Linear issue to Tessl, or adding the “tessl” label to a GitHub issue, starts the work.

Describe the change, constraints and acceptance criteria.

The Ticket to PR loop picks up the ticket, runs it through your factory and opens a pull request.
Connect Tessl Code Review, Verifiers and Vulnerability Remediation to review the code, check your standards and address security findings. Tessl can work through review feedback and update the PR.
Your team checks the result and decides when it’s ready to ship.

Set up your Tessl Factory

skills/frontend-standards/SKILL.md

Frontend skillv4

## ComponentsBuild form fields from the design system.Use tokens for color and spacing, never raw hex.## DependenciesNew packages need a clean Snyk scan.## ReviewEvery form field has a visible label.

TES-187 · Add date picker to report filters

frontend-standards v4

AGENTS.md

Verifiers3 of 3 pass

Form fields come from the design system

No raw hex values

Date range field has a visible label

Give every ticket your team’s engineering context

Acceptance criteria describe the outcome. Your team’s skills and repository instructions give agents the context to implement it.

Write your standards once
Keep coding conventions, architectural guidance and review requirements in reusable, versioned skills.
Put those standards to work
Guide implementation with your team’s context, then configure Code Review and Verifiers to check the result.
Improve the instructions behind the work
Use review findings to identify gaps. Evaluate skill changes on representative tasks before rolling out an updated version.

Keep work moving through review

Opening a PR is one step. Getting it ready to merge takes iteration.

Tessl can respond to review feedback and update pull requests created by your factory. Your team stays involved where judgment matters, with the final merge decision in your hands.

Set up Tessl Code Review

Add date picker to report filters#2843Ready for your approval

Tessl opened PR #2843From TES-187 · 4 files changed
Code Review requested a changeMediumDateFilter.tsx: the end date can be set before the start date.
Tessl pushed a fixValidate the date range before applying the filter · a3f9c21
Code Review and Verifiers passedFinding resolved. All required checks pass.
Your team approves and mergesThe final merge decision stays with you.

Start with one workflow. Build from there.

Set up Ticket to PR for one repository, then connect the review and verification loops your team needs.

Start

Ticket to PR on one repository

Set up Ticket to PR for one repository and run it on a bounded ticket.

Connect

The review and verification loops you need

Add Code Review, Verifiers and Vulnerability Remediation to check every change.

Scale

A rollout across teams

Work with Tessl to choose a first use case, define standards and checks, and scope a pilot around your engineering workflow.

Planning a rollout across teams? Work with Tessl to choose a first use case, define standards and checks, and scope a pilot around your engineering workflow.

Discuss an enterprise rollout Set up your Tessl Factory

Keep exploring

Get practical insights from the Tessl blog, explore demos and event replays on YouTube, and hear from builders on the AI Native Dev podcast.

Context-Driven Factories

Software factories are the frontier of agentic software development. They promise a compounding development process that gets cheaper, faster, and better every week. But most teams struggle to build factories that deliver these compounding outcomes. Their buildout stalls, or the gains are merely incremental.

Read article

Engineering a Context-Driven Software Factory

Explore how context-driven software factories enable agents to handle complex tasks, requiring engineering practices to ensure reliable decision-making and automation.

Read article

Tutorial · Docs

Improving agent code quality

Turn recurring agent mistakes into better skills, rules and checks.

Open the tutorial