القائمة
Review and improve names for variables, methods, classes, files, routes, booleans, units, and paired operations.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review AI-assisted code changes for continuation bias, missing context, architectural asymmetry, security gaps, and code ownership.
Review method and object APIs for argument count, option shape, boolean flags, object parameters, and fluent configuration.
Identify small, reusable components that can be isolated from a large codebase without prematurely forcing microservices.
Review error handling, logging, exception clarity, and debugging seams so failures stay visible and testable.
Simplify control flow with early returns, shallow nesting, explicit conditions, and readable branching.
Review whether code works with framework conventions instead of fighting them with unnecessary abstractions, mixed ecosystems, or upgrade-hostile choices.
| name | dandy-code-naming-review |
| description | Review and improve names for variables, methods, classes, files, routes, booleans, units, and paired operations. |
| argument-hint | [file, diff, or code snippet] |
Use this skill when a user asks whether names are clear, requests renaming help, or shares code with vague, misleading, mixed-language, or inconsistent identifiers.
The output should propose concrete names and explain the decision rule behind each important rename.
-er roles.is, has, can, or should.start/finish, begin/complete, open/close.This skill may read source files and propose or apply renames when requested. Treat broad naming conventions and project rules as read-only unless the user explicitly asks to update them.
Generated review text follows project artifact language when configured. Identifier suggestions should match the dominant language and framework conventions in the codebase.