Analyze git history and code to identify design flaws and scope drift.
npx skills add https://github.com/axel-kaliff/dotfiles --skill rethink-axel-kaliff
Please help me install this Agent Skill. Skill: rethink Source: https://github.com/axel-kaliff/dotfiles/tree/main/claude/.claude/skills/rethink Command: npx skills add https://github.com/axel-kaliff/dotfiles --skill rethink-axel-kaliff
This Skill helps developers and reviewers pause development and critically evaluate whether the current codebase, branch direction, and dependency choices are justified, or if a redesign or targeted refactor is warranted. It surfaces scope drift, stacked patches, dependency bloat, and design-level mismatches between problem and implementation.
Run the rethink skill on a feature branch or directory to receive a concise retrospective, targeted design critique, and an actionable clean-slate recommendation.
High-intent search queries and answers about installing and using this skill.
A branch retrospective analyzes git history to classify commits as original-goal, pivot, patch, or scope-drift, surfacing repeated fixes that indicate missed design insights. It helps reviewers evaluate whether the current branch direction is justified before merging.
Scope drift occurs when a branch accumulates changes beyond its original goal. You can detect it by analyzing git history to classify commits as original-goal, pivot, patch, or scope-drift, which highlights repeated fixes and design-level mismatches between the problem and implementation.
To audit dependencies and duplication, run an analysis that flags unnecessary or heavy packages and identifies duplicated code clusters. This audit provides a size inventory to help prioritize targeted refactors and reduce dependency bloat in the codebase.
You should perform a design critique when planning a refactor, before merging a feature branch, or when code feels over-engineered. It evaluates abstractions, single-responsibility, accidental complexity, scalability risks, and file-level complexity hotspots to justify a redesign.
Yes, you can analyze accidental versus essential complexity by reading prioritized files within specific directories. The analysis evaluates abstractions, single-responsibility, and file-level complexity hotspots to distinguish unnecessary implementation difficulty from inherent problem complexity.
The best way to generate a clean-slate design proposal is to synthesize analyzed git history and prioritized file data into actionable recommendations. This approach identifies design mismatches and scope drift to produce a concrete redesign proposal for targeted refactoring.
sfc-gh-dflippoSynchronizes AI agent skills from local SKILL.md files and remote Git repositories.
aromanarguelloDetect duplicated code, dead code, and unnecessary abstractions with file:line references.
jackmcintyreAnalyze Python code for complexity, duplication, and best practices.
bejranondaDefine and enforce code quality standards for Python and JavaScript/TypeScript projects.
