---
title: "no-achievement-language"
description: "Flags achievement language and hype in reports, PRs, and docs."
sidebar:
  label: "no-achievement-language"
  badge: "Hard"
search:
  tags: [rule, static, style]
---

| Property | Value |
| -------- | ----- |
| Kind | Hard rule |
| Engine | `phrase` |
| Tier | `static` |
| Severity | `warning` |
| Intent | `style` |
| Scope | `text` |

:::note
This is a style rule. It reports findings and participates in `--fix`, but never moves the [human-likeness score](/docs/concepts/scoring).
:::

## Why

Prose should state what changed and why. Words like “successfully”, “comprehensive”, and “flawless” praise the work instead of describing it, and are the tell of AI-written status updates. Say what happened; let the reader judge it.

## Examples

<Columns cols={2}>
  <Column>
    **Flagged**

    Successfully implemented comprehensive error handling to ensure reliable performance.
  </Column>
  <Column>
    **Better**

    Added error handling to every API endpoint.
  </Column>
</Columns>

## Turning it off

```sh
lawlint --disable no-achievement-language draft.md
```

Or durably, in `.lawlint/config.json` — see [Configuration](/docs/reference/configuration).