# Turn a framework build warning category into an error

A warning category everyone scrolls past, cleared and then promoted to an error.

Category: Audits and budgets
Source: https://letsship.ai/use-cases/turn-build-warnings-into-errors
Published: 2026-08-25

## Goal

Clear one category of build warnings and promote it to an error.

## Acceptance criteria

- Every warning in the category is fixed
- The category is promoted to an error
- A seeded warning fails the build
- Nothing is suppressed to reach zero

## What lands as proof

A seeded warning failing the build, which is what stops the category refilling next week.

## Prompt

Copy this to an agent to open the ticket:

```text
Create a Linear issue in my team and assign it to the SHIP agent.

Title: Make {warning} an error

Description: Clear one category of build warnings and promote it to an error.

Acceptance criteria:
- Every warning in the category is fixed
- The category is promoted to an error
- A seeded warning fails the build
- Nothing is suppressed to reach zero

Before you create the issue, count this repository's build warnings by category and replace {warning} with the most common one.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: clear one category of build warnings and promote it to an error. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.

### How do I know the work is done?

The pull request carries the evidence, not only the diff. Here that means the category reads empty and the build fails if it returns, so a reviewer can confirm the result without reproducing the work locally.

### How much oversight does this need?

The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.