Code Review & Refactoring

Build a visual canvas for reviewing a pull request or branch diff with risk callouts

Open code changes in the difit local diff viewer for a review on request

Review a branch, commit or GitHub PR and post findings inside the difit viewer

Review the current change diff for correctness, security and edge cases

Review a plan, PR or change from an outsider view and trace the real code path

Review a proposed change for regressions, unmet requirements and security risks

Get an advisory Cursor Composer second opinion on a diff before merging

Review code, plans and scope for quality and security from several angles

Reduce complexity and sharpen module boundaries with software design rules

Improve naming, function design and readability in everyday code

Apply construction rules to routines, control flow, defensive code and tests

Restructure existing code step by step while keeping its observable behavior

Spot code smells and pick refactoring techniques without over-redesigning

Run dart analyze and auto fix lint issues before committing changes

Refactor Dart if-else chains and JSON parsing with pattern matching

Write and migrate Dart primary constructors and concise constructor syntax

Check a benchmark for limits, noise and relevance before reporting a speedup

Find what a small diff could break elsewhere and prove it by running code

Stress test code changes with independent reviewers to expose blind spots

Audit code comments with a reviewer and fix the findings you accept

Check what limits a measured number before reporting a speedup or regression

Favor deletion and the smallest change when refactoring or adding abstractions

Migrate all callers and delete the old API in one wave, without shims

Collapse one-caller wrappers and shrink mutable scope so code is easy to trace

Delete dead code and stub references before building new features on top

Make illegal states unrepresentable and parse external data at boundaries

Apply TypeScript best practices whenever you edit TypeScript or TSX files

Answer how and where questions about repo behavior with the jg search CLI

Check web code for security gaps, outdated patterns and compatibility problems

Run a Lighthouse-style web quality audit across speed, accessibility and SEO

Review diffs and files for OWASP issues, error handling, complexity and speed

Strip AI-generated bloat, extra comments and over-engineering from your branch diff

Find the smallest structural fixes for tangled code and dependency cycles

Run pre-commit checks, a security scan and a reviewer subagent before pushing code

Open file diffs and file comparisons in VS Code for the user to review

Update project dependencies safely and fix dependency issues in any language

Suggest clearer variable, function and class names that fit codebase conventions

Shrink a codebase by deleting code, measuring success by final size

Decide when to use factory, strategy, chain of responsibility and other design patterns

Guide a slow, tangled codebase toward fast, bounded and readable architecture

Write readable code with clear naming, small functions and clean error handling

Take a vibe-coded prototype to production with tests, clean structure and resilience

Apply software craftsmanship principles like DRY, tracer bullets and contracts

Apply named refactorings like extract method to improve code without changing behavior

Pay down a large aging codebase in place into one that is safe to change

Manage complexity with deep modules, information hiding and strategic design

Upgrade an app from Workflow SDK 4.x to 5.0 and fix removed v4 APIs

Upgrade a custom Workflow SDK World implementation to the v5 spec

Profile and speed up WordPress backends through query, cache and option tuning