How to disable naming convention warnings?

[cxcorp]

The naming convention enforcement does not work for me. For example, when creating a function named GameApp_InitInstance_candidate through the MCP, I get back warnings:

"Function name 'GameApp_InitInstance_candidate' — main part 'GameApp_InitInstance_candidate' is not PascalCase. Expected: GameappInitinstanceCandidate"
"Function name 'GameApp_InitInstance_candidate' — main part 'GameApp_InitInstance_candidate' contains underscores. Use PascalCase after the module prefix."
"Function name 'GameApp_InitInstance_candidate' does not start with a recognized verb. First word 'Game' not in allowed list. Common verbs: Get, Set, Initialize, Process, Calculate, Find, Check, Handle"

The first part about the pascalcase miiiight be debatable, but the last one about the function not starting with a verb is very hard for me to understand. What is the recommended naming for such a case where we are trying name e.g. a vtable function name or other opaque loosely related prefixed function?

[bethington]

Two things that I think clear this up:

1. The warnings are advisory, not blocking. The function was actually renamed successfully — the response includes status: "success" alongside the warnings array. Anything in warnings is just a flag for review; it does not roll back the operation. So your GameApp_InitInstance_candidate rename did go through.

2. For module-prefix style names (vtable methods, opaque containers, etc.), use an UPPERCASE_ prefix followed by _. The validator recognizes this pattern (NamingConventions.MODULE_PREFIX = ^[A-Z]+_[A-Z].*) and strips the prefix before applying the PascalCase / verb-first checks to the remainder. So GAMEAPP_InitInstanceCandidate (uppercase module prefix, PascalCase main part starting with the verb Init) validates cleanly. GameApp_… mixes case in the prefix, which is why the stripper does not match and the underscore-bearing main part trips three rules at once.

There is currently no off-switch to silence the warnings entirely. If a flag (e.g. GHIDRA_MCP_SKIP_NAMING_WARNINGS=1) would be useful for your workflow, open an issue and I will wire it up — it is a small change.

[cxcorp]

Okay, thank you. I think a flag would be useful so that the agent doesn't need to spend tokens every time thinking about "This is only a warning and I can ignore it"