Analyze git merge-base diffs and produce a ranked PLAN.md simplification plan.
npx skills add https://github.com/hamzaPixl/pixl-ai --skill cto-review
Please help me install this Agent Skill. Skill: cto-review Source: https://github.com/hamzaPixl/pixl-ai/tree/main/packages/crew/skills/cto-review Command: npx skills add https://github.com/hamzaPixl/pixl-ai --skill cto-review
This Skill identifies and quantifies architectural and data-flow complexity in a branch diff, prioritizing algorithmic and pipeline simplifications over cosmetic changes to reduce long-term maintenance burden and runtime inefficiencies.
Run a CTO-level review of the current branch diff against a base ref and produce a ranked, line-numbered PLAN.md with concrete simplification steps.
High-intent search queries and answers about installing and using this skill.
To review a git branch diff for architectural complexity, analyze the merge-base scoped diff to identify data-flow redundancies and structural smells. This produces a ranked simplification plan with exact file paths and line numbers, prioritizing behavior-preserving changes over cosmetic edits.
A merge-base scoped diff compares the current working tree, including staged, unstaged, and untracked production files, against a base git reference. You need it for code review when preparing a branch for a large refactor or release to ensure high-impact, verifiable simplifications.
Generate a ranked simplification plan from a code diff by analyzing data-flow and algorithmic issues such as redundant passes and state duplication. The output is a verifiable PLAN.md containing independent, shippable phases with concrete line-count eliminations and exact citations.
Yes, automated architectural review can find algorithmic and data-flow smells by prioritizing pipeline issues over cosmetic changes. It requires exact file paths and line numbers, excludes test code, and quantifies complexity to reduce long-term maintenance burden and runtime inefficiencies.
Limitations of using git diffs for structural code analysis include the exclusion of test code from the review scope and the requirement for exact merge-base diffs. Analysis is strictly scoped to production files, meaning untested edge cases or non-production environments are not evaluated.
Yes, cto-review works with untracked production files by including them in the merge-base scoped diff alongside staged and unstaged changes. It analyzes these files to identify data-flow and structural smells while explicitly excluding test code from the architectural review.
prateekMerge Codex review and PAL codereview outputs into a prioritized feedback report.
marcusgollGenerate an assumption inventory, codebase analysis, and simplified architecture plan.
fubiraDetect code smells and propose refactoring patterns for Go and TypeScript/React projects.
raybargasDetect and fix coding style violations across multi-language repositories.
