# Rename a concept across code, tests, fixtures, and documentation

A name the product stopped using, updated everywhere including the places a search misses.

Category: Refactors and cleanup
Source: https://letsship.ai/use-cases/rename-a-concept-everywhere
Published: 2026-08-25

## Goal

Rename a concept consistently across code, tests, fixtures, and documentation.

## Acceptance criteria

- No occurrence of the old name remains outside migration history
- Database columns and API fields are handled explicitly, with compatibility if needed
- Documentation and comments are updated too
- The rename introduces no behaviour change

## What lands as proof

A repository-wide search returning nothing, with the deliberate exceptions listed.

## 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: Rename {old} to {new} everywhere

Description: Rename a concept consistently across code, tests, fixtures, and documentation.

Acceptance criteria:
- No occurrence of the old name remains outside migration history
- Database columns and API fields are handled explicitly, with compatibility if needed
- Documentation and comments are updated too
- The rename introduces no behaviour change

Before you create the issue, name the old and new terms and count the occurrences in this repository. Replace {old} and {new}.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: rename a concept consistently across code, tests, fixtures, and documentation. 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 nothing references the old name anywhere in the repository, 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.