# Enable one lint rule and clear every violation in one directory

A rule the team agreed on, switched on for one directory with every violation fixed rather than suppressed.

Category: Type safety and lint rules
Source: https://letsship.ai/use-cases/enable-one-lint-rule
Published: 2026-08-25

## Goal

Enable one lint rule for one directory and fix every violation it reports.

## Acceptance criteria

- The rule is enabled for the directory and the build is green
- Every violation is fixed rather than suppressed
- No new suppression comments are added
- The remaining directories are counted in the description

## What lands as proof

A green build with the rule on and no suppressions added, which is what separates enabling from silencing.

## 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: Enable {rule} for {directory}

Description: Enable one lint rule for one directory and fix every violation it reports.

Acceptance criteria:
- The rule is enabled for the directory and the build is green
- Every violation is fixed rather than suppressed
- No new suppression comments are added
- The remaining directories are counted in the description

Before you create the issue, list the rules this repository has disabled or warned rather than errored, and replace {rule} and {directory}.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: enable one lint rule for one directory and fix every violation it reports. 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 rule enabled, suppressions removed, build green, so a reviewer can confirm the result without reproducing the work locally.

### How much oversight does this need?

None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.