# `cli.declines_arguments`

A `jadpo declines` command names no action, one it doesn't have, or a rule or path that isn't the project's.

Area 14, [Tools](/docs/tooling.md); not declinable; the next step is usually the agent's.

## Why Jadpo refuses it

`jadpo declines list` shows the findings declined with a reason, and `clear` removes them so each comes back. Clearing is done to the declines you name, so a rule that doesn't exist is refused rather than treated as none.

## What it looks like

The rule given to `--rule` is misspelt:


```sh
jadpo declines list --rule type.standard_exist
```

```text
error: `type.standard_exist` isn't a rule
  reason: Jadpo has no rule `type.standard_exist`. Did you mean `type.standard_exists`?
  next: Use `--rule type.standard_exists` (agent)
  rule: cli.declines_arguments
  help: https://jadpo.dev/docs/errors/cli.declines_arguments
```

`(agent)` at the end of the `next:` line means your coding agent can make the fix itself.

An action it doesn't have is refused with the ones it does:

```sh
jadpo declines remove
```

```text
error: `remove` isn't something `jadpo declines` does
  reason: `jadpo declines` can `list` or `clear`.
  next: Run `jadpo declines list` to see every decline (agent)
  rule: cli.declines_arguments
  help: https://jadpo.dev/docs/errors/cli.declines_arguments
```

## How to fix it

**If you meant the rule it suggests**, use it:

```sh
jadpo declines list --rule type.standard_exists
```

It lists that rule's declines with their reasons.

## Related

- [`jadpo declines list` and `clear`](/docs/commands-for-records-findings-and-review.md#jadpo-declines-list-and-clear)
- [Listing and clearing declines](/docs/declining-a-judgement-call.md#listing-and-clearing-declines)