Results for “refactoring”

Rewrites unprofessional code comments into clear ones and performs non-semantic cleanup without altering logic or behavior.

Coordinates five specialized coding agents (linter, perf, refactor, security, test) to enforce quality gates across the development lifecycle, from lint enforcement through performance profiling, refactoring, security auditing, and test coverage.

Classifies code review findings to choose the smallest correct response, preventing one-patch-per-comment churn.

Forces investigation of file dependencies before editing code to prevent cascade failures.

Provides a structured protocol for receiving and evaluating code review feedback, emphasizing technical verification over performative agreement.

Write readable, maintainable code through disciplined naming, small functions, and clean error handling.

Runs three parallel reviewer agents over recent code changes, aggregates their findings, and applies the fixes worth applying.

Enforces dense, correct, and idiomatic code on all coding tasks, minimizing code bloat and agent operation overhead.

Compares two code versions for semantic equivalence by tracing both side-by-side, identifying divergences, and producing a structured verdict.

Guides incremental code improvements, error-proofing through types and validation, and standardization for higher code quality.

Enforce idiomatic Rust patterns for ownership, error handling, enums, traits, concurrency, and best practices to build safe, performant applications.

Scans recently changed code for tech debt: duplicated logic, dead code, magic numbers, deep nesting, and TODOs, then proposes fixes.

Guides incremental code improvements, error-proofing through types and validation, and standardization for higher quality and fewer defects.

Transforms working code into clean, readable, and maintainable code following Robert C. Martin's principles.

Reviews a codebase for structural smells and refactors them with provable safety, using micro commits and green-bar discipline.

Applies four disciplined mindsets—audit, debt, help, review—to cut complexity, track deferrals, surface reference, and catch over-engineering in codebases.

Conducts multi-axis code review across correctness, readability, architecture, security, and performance before merging any change.

Analyzes code diffs and files to identify bugs, security vulnerabilities, code smells, and architectural concerns, producing a structured review report with prioritized, actionable feedback.

Organizes 70+ React and Next.js performance optimization rules across 8 priority categories for use when writing, reviewing, or refactoring code.

Reviews code through the lens of 12 classic software engineering books, catching design smells, coupling issues, and architectural risks that linters miss.

Review git diffs or file scopes for code reuse, quality, efficiency, and clarity issues, then optionally apply safe, behavior-preserving fixes.

Turns a GitHub pull request into a code-change explainer video with changelog, feature reveal, or refactoring walkthrough built from the diff, commits, and files.

Runs three parallel reviewers to find code reuse, quality, and efficiency issues in a diff, then applies safe fixes and reports risky ones.

Mines a codebase for evidence-backed improvement opportunities, forcing two escalation gates to surface breakthrough ideas, and outputs a ranked portfolio with a plan seed without implementing.

Enforces an algorithm-first discipline: state Big-O, data structure, and algorithm family before writing loops, queries, or recursion to catch O(n²), N+1, and brute-force defaults.

Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, macOS-specific APIs, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.