code-optimizer

Audit PR diffs and implement 3–5 optimizations across frontend, backend, and patterns.

Updated Aug 6, 2025
One-click install
npx skills add https://github.com/fabiano001/claude-config --skill code-optimizer-fabiano001
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-optimizer
Source: https://github.com/fabiano001/claude-config/tree/main/skills/code-optimizer
Command: npx skills add https://github.com/fabiano001/claude-config --skill code-optimizer-fabiano001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews only the changes on a feature branch (PR diff) and proposes 3–5 concrete optimizations—frontend, backend, and best-practices/patterns—then implement them through a plan-review loop and TDD-first execution. Shell usage follows Claude Code tool permissions.

Core Features & Use Cases

  • Analyze PR diffs to identify optimization opportunities across FE and BE
  • Generate 3–5 concrete optimizations covering frontend, backend, and best practices
  • Execute changes through a plan-review loop with TDD-first validation and tests

Quick Start

Provide the branch to optimize (or CURRENT) and an optional focus, and I will generate a 3–5 optimization plan and run the plan-review and execution loop.

Frequently Asked Questions about code-optimizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I optimize PR diffs for feature branches automatically?

Auditing PR diffs to optimize feature branches involves analyzing changes and proposing 3–5 concrete optimizations across frontend, backend, and patterns. The process executes changes through a plan-review loop validated by TDD-first tests and benchmarks.

Can I use a TDD-first workflow to refactor and improve code readability?

TDD-first workflow refactors code by validating optimizations with tests and benchmarks before execution. It ensures code readability, performance, and maintainability improvements are implemented through a structured plan-review loop.

What is the best way to analyze a feature branch diff for performance improvements?

Analyzing a feature branch diff for performance improvements requires auditing the changes to identify optimization opportunities. It generates 3–5 concrete suggestions covering frontend, backend, and best practices to improve outcomes.

Does the code optimization process cover both frontend and backend changes?

The code optimization process covers both frontend and backend changes by auditing PR diffs. It proposes concrete optimizations across FE, BE, and best-practice patterns, ensuring performance, readability, and maintainability improvements.

How many concrete optimizations are generated from a diff analysis?

Diff analysis generates 3–5 concrete optimizations targeting frontend, backend, and best practices. These suggestions are then implemented through a plan-review loop with TDD-first validation.

Do I need to provide the entire codebase to get optimization suggestions?

You do not need to provide the entire codebase; the optimization focuses on reviewing only the changes on a feature branch or PR diff. Provide the branch name or CURRENT with an optional focus to generate the optimization plan.