القائمة
Identify small, reusable components that can be isolated from a large codebase without prematurely forcing microservices.
التثبيت باستخدام 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.
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.
Review and improve names for variables, methods, classes, files, routes, booleans, units, and paired operations.
| name | dandy-code-component-extraction |
| description | Identify small, reusable components that can be isolated from a large codebase without prematurely forcing microservices. |
| argument-hint | [repository area, module, class, or refactor goal] |
Use this skill when a user asks how to reduce cognitive load in a large monolith, isolate reusable code, extract a package, or make a subsystem easier to understand.
The output should propose small, testable boundaries with clear responsibilities, not a broad rewrite.
This skill may read source, tests, dependency manifests, and README files. It may propose or apply extraction edits only when the user asks for implementation. Do not create new repositories or publish packages without explicit approval.
Use configured artifact language for plans and generated documentation. Keep package, namespace, and API names consistent with the project ecosystem.
