# Delete unreachable code the coverage report and call graph confirm

Code both tools agree nothing can reach, removed with the build output measured either side.

Category: Dead code and stale content
Source: https://letsship.ai/use-cases/delete-unreachable-code-confirmed
Published: 2026-08-25

## Goal

Remove code that coverage and the call graph both confirm is unreachable.

## Acceptance criteria

- Both sources of evidence are attached
- The suite passes
- Output size is recorded before and after
- Reflection and configuration-driven access are checked separately

## What lands as proof

Two independent tools agreeing, plus a smaller build artefact.

## 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: Delete unreachable code in {area}

Description: Remove code that coverage and the call graph both confirm is unreachable.

Acceptance criteria:
- Both sources of evidence are attached
- The suite passes
- Output size is recorded before and after
- Reflection and configuration-driven access are checked separately

Before you create the issue, run coverage and a call-graph check over this repository and replace {area} with the region they agree on.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: remove code that coverage and the call graph both confirm is unreachable. 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 suite green, build output measurably smaller, 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.