Canonical: https://botbento.com/usecases/code-file-naming-and-comment-convention-checker/
Format: Markdown representation of the public HTML page.

# Code file naming and comment convention checker

[Coding](https://botbento.com/usecases/coding/) · Intermediate

Review new code files for naming and comment standards

An AI bot watches for newly created code files and changed comments. It checks them against team naming and documentation rules and prepares a small draft patch with suggested filenames and comment text. It flags unclear cases instead of guessing, so a developer can review the cleanup before anything changes.

## Quick answers

**What does it do?** Review new code files for naming and comment standards. Result: Draft rename and comment patch for.

**What does it need?** Tools: Terminal. Intermediate: some setup. The prompt includes an approval step.

**How do I run it?** When something happens: New code file detected. Copy the prompt below into a bot in BotBento.

## How it works

1. When something happens: New code file detected
2. Then: Compare filename and comments to team
3. Result: Draft rename and comment patch for

## Prompt to start with

```text
You are a code convention bot. When a new code file appears or a comment changes, compare the filename and comment text with the team rules supplied by the user. Propose a compliant filename and concise comment additions. Flag ambiguous cases and ask for clarification. Do not rename, edit, move, commit, send, pay, or delete anything without the user's explicit approval; present every proposed change as a draft for review.
```

## Tools it uses

Terminal

## Works with

BotBento

## Tags

code-review, conventions, automation, developer-tools

## Source

[Cursor and Claude Opus 4.5 is a game changer](https://news.ycombinator.com/item?id=46185230) — Hacker News · checked 2026-11-13

Summarized in our own words. Any results described there are the authors’ own, not measured by BotBento.

Verified 2026-11-13: passed every automated gate and a second-model review (kimi-code/k3.1-pro). Automated, not human review. [How verification works](https://botbento.com/usecases/verification/)

By BotBento Editorial · Added 2026-11-13 · Updated 2026-11-13 · [Suggest a correction](https://botbento.com/contact/)

## Related use cases

- [Pull request convention and hygiene checker](https://botbento.com/usecases/pull-request-convention-and-hygiene-checker/) — Enforce repository contribution standards and identify stale pull requests automatically
- [Stage code changes for human review before merging](https://botbento.com/usecases/autonomous-coding-task-staging-and-review-gate/) — Summarize pending diffs and hold commits until a developer approves
- [Exporting terminal coding sessions into pull request notes](https://botbento.com/usecases/exporting-terminal-coding-sessions-into-pull-request/) — Convert raw agent commands, prompts, and file diffs into clean review documentation
