review-and-refactor

Invoke the review-and-refactor skill with a target scope, such as a module or the full project. It reads your coding guidelines, reviews code for quality, security, and testing issues, then applies prioritized refactorings and verifies tests still pass.

The review covers naming conventions, single responsibility, DRY violations, error handling, hardcoded secrets, input validation, and test coverage. For MCP servers it also checks tool naming, annotations, pagination metadata, and response formats.

Yes, it includes MCP-specific checks such as snake_case tool naming with service prefixes, tool annotations like readOnlyHint and destructiveHint, pagination metadata for list operations, and JSON plus Markdown response format support.

Issues are ranked into three tiers: critical items like security and correctness first, then important items like quality and tests, and finally readability suggestions. Refactorings keep the existing file structure intact and tests are verified after changes.

Avoid it for large architectural redesigns or greenfield design decisions, since the process preserves existing file structure. It is best suited for incremental quality, security, and convention improvements on existing code.