# Add a missing gate: typecheck, lint, or a coverage floor

A check the team runs locally and the pipeline does not, added so it stops being optional.

Category: Pipeline speed and cost
Source: https://letsship.ai/use-cases/add-a-missing-pipeline-gate
Published: 2026-08-25

## Goal

Add a missing verification gate to the pipeline.

## Acceptance criteria

- The gate runs on every pull request
- A deliberately seeded violation fails the build
- Existing violations are fixed before the gate is enforced
- The gate runs early enough to fail fast

## What lands as proof

A seeded violation failing the build, which is what makes it a gate rather than a report.

## 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: Add the {gate} gate to CI

Description: Add a missing verification gate to the pipeline.

Acceptance criteria:
- The gate runs on every pull request
- A deliberately seeded violation fails the build
- Existing violations are fixed before the gate is enforced
- The gate runs early enough to fail fast

Before you create the issue, list which checks this repository runs locally but not in the pipeline and replace {gate}.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: add a missing verification gate to the pipeline. 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 approved on the plan, then the gate fails on a seeded violation, so a reviewer can confirm the result without reproducing the work locally.

### How much oversight does this need?

The run stops for the plan, and the review bar is raised afterwards so that smaller suggestions block the merge too, not only serious findings.