[DOCS] `/bug` (`/feedback`) command table shows the report argument as optional; v2.1.178 makes the description required

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/commands

Section/Topic

Slash commands table — the /feedback [report] row, which lists /bug and /share as aliases.

Current Documentation

The commands table row reads:

| /feedback [report] | Submit feedback, report a bug, or share your conversation. Aliases: /bug, /share |

The square brackets around report indicate the argument is optional. The description also does not mention that a description now drives the GitHub issue title.

What's Wrong or Missing?

The v2.1.178 changelog says: "/bug now requires a description before submitting, and no longer uses model-refusal text as the GitHub issue title." The command-table row still documents /bug (and its /feedback / /share aliases) as taking an optional [report] argument, and never mentions the title-generation behavior change.

There are two distinct documentation gaps:

A. Required-argument syntax is wrong

Other rows in the same table use the convention <arg> for required arguments and [arg] for optional ones (for example, /cd <path> is required, /clear [name] is optional). After v2.1.178, report is required for /bug, so the row should use <report> (or equivalent wording) instead of [report]. Without that fix, readers comparing the table to the new behavior will be confused when /bug with no description refuses to submit.

B. Title-generation behavior is undocumented

The changelog also says /bug "no longer uses model-refusal text as the GitHub issue title." That is a user-visible behavior change — the title shown in the prefilled GitHub issue now comes from the description the user writes, not from whatever the model would have produced. Nothing in the /feedback row, the errors.md "Report an error" section, or the data-usage.md discussion of /feedback describes this. Readers who care about what their GitHub issue will be titled have to dig into the changelog to find out.

Suggested Improvement

Update the /feedback row in docs/code.claude.com/docs/en/commands.md so it reflects v2.1.178 behavior.

Before:

| /feedback [report] | Submit feedback, report a bug, or share your conversation. Aliases: /bug, /share |

After:

| /feedback <report> | Submit feedback, report a bug, or share your conversation. The report description is required and is used as the title of the prefilled GitHub issue. Aliases: /bug, /share |

That single edit:

• Switches the argument notation from optional ([report]) to required (<report>) to match the other rows in the table.
• Surfaces the new title-generation behavior in the same place users look up the command, so they don't have to read the changelog to learn that the description they type becomes the issue title.

Optionally, also add one sentence to the "Report an error" section in errors.md that points back to this behavior, e.g. "The description you type becomes the title of the prefilled GitHub issue (changed in v2.1.178; previously the title was derived from model output)."

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:
| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/commands | 76 | Slash-commands table row for /feedback [report] |
| https://code.claude.com/docs/en/errors | 712, 724 | "Report an error" section mentions /feedback but does not describe the new required-description or title-generation behavior |

Total scope: 2 pages affected (same root cause on both: docs for the /feedback//bug command not yet updated for v2.1.178).

Changelog reference: v2.1.178 (June 15, 2026) — "/bug now requires a description before submitting, and no longer uses model-refusal text as the GitHub issue title."

Why this is a documentation issue and not just a changelog entry: The command-table row is the canonical reference for /bug//feedback syntax across the docs site. After v2.1.178, the documented syntax ([report], optional) directly contradicts runtime behavior (description required, drives the issue title). A user following the table will hit the new prompt for a description with no warning, and will not learn from the docs that the description becomes the GitHub issue title.