> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Review and repair pipeline records

> Ask your agent to review pipeline records and propose repairs.

[Agent guide: CLI and SDK instructions →](/docs/guides/pipeline-hygiene)

## 1. Have your context ready

Have opportunity IDs, stage and next-step rules, activity evidence, and the fields your team permits updating.

## 2. Ask your agent

Paste this into your agent, then provide your task and example inputs when it asks:

```deepline-prompt theme={null}
/deepline-gtm Review these pipeline records with Deepline. Compare recorded stage, owner, next step, and dates with the evidence available. Separate missing data, stale activity, contradictions, and operational errors. Return field-level proposals with reasons and unresolved questions. Keep stage changes, commercial terms, and ownership decisions for human review. Do not change the CRM or trigger follow-ups automatically.
```

Complete any requested sign-in yourself. Give the agent the missing information before approving execution. Provider-backed work can incur usage.

## 3. Review the result

A stale record is flagged under your stated rule, not declared lost without evidence. Approved repairs retain the original record identity and are read back after writing.

Ask your agent:

```deepline-prompt theme={null}
/deepline-gtm Compare the result with the acceptance rule we agreed. Show the evidence for accepted and rejected outcomes, unresolved questions, and recorded Deepline usage where work ran. If work is still running or a response is uncertain, inspect the original saved execution before proposing another request. Explain the next decision I need to make.
```

Approve a larger job, recurring work, or external changes only after reviewing that decision.

## Check your understanding

Should automation advance a deal stage just to improve completeness?

> **Show the answer**
>
> No. Commercial changes need evidence and authority. Keep the disputed field
> visible for the appropriate decision.

## Related guides

* [Write Plays](/docs/human/sdk-v2/plays)
* [Batch CSV enrichment](/docs/human/sdk-v2/batch-csv)
* [CRM data quality automation: validation and safe writes](/docs/human/guides/crm-data-quality-automation)
* [Understanding revenue data quality](/docs/guides/revenue-data-quality)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.