[Code Quality] Defines clear boundaries and goals for a refactoring session. Use to establish what WILL and WILL NOT change, set success criteria, and create a focused refactoring…
Acts as a Bash scripting expert that creates and refactors Shell scripts with clean structure, standard conventions, strong error handling, logging, and production-ready — from…
Refactorizar un SKILL.md demasiado largo o mal estructurado extrayendo ejemplos a references/EXAMPLES.md, dividiendo procedimientos compuestos y reorganizando secciones para una…
Team-based code refactoring with analysis and user-approved changes. Use when: "refactor this code", "リファクタリング", "コード整理", "refactor team", "リファクタチーム".
Proves a behavior-preserving code change (refactor, rename, split, merge, extract, inline, or delete of confirmed-dead code) is actually complete.
Review code for refactorability — surface concrete, prioritized refactoring opportunities grounded in Martin Fowler's smell catalog and SOLID, augmented with static analysis tools…
Systematic refactoring with small-step discipline. Use when user says 'refactor', 'clean up', 'restructure', 'extract', 'rename', 'simplify', or mentions code smells.
Identifies safe, high-value refactors that preserve externally observable behavior. Use for debt, smells, or “clean this up” asks.
Guidelines for maintaining a clean codebase through limits and abstraction. Use when a file or component becomes difficult to read.
Execute refactoring safely with test-first verification following best practices. Takes refactoring discovery reports as input and performs incremental refactoring with continuous…
SOTA refactoring and modularization principles that LLMs systematically miss. Covers language-agnostic principles plus Rust-specific (visibility, crate boundaries, Cargo features)…
Use when actively refactoring an existing codebase's package or module structure. Detects cycles, oversized modules, misplaced responsibilities, and dependency direction problems,…
Plan a safe, incremental refactor of messy code without changing behavior. Use when code needs restructuring, is hard to change, has grown tangled, or you want to clean it up…
Strukturierte Refactoring-Planung mit Impact-Analyse und schrittweiser Umsetzung für große Codebases.
Expert in improving code structure without changing behavior. Specializes in Design Patterns, SOLID principles, and Anti-Corruption Layers.
Systematic refactoring methodology with safety guarantees for polyglot codebases. TRIGGER when: user asks to refactor code, restructure a module, split a monolith, do a large…
Expert code refactoring specialist for improving code quality without changing behavior. Activate on: refactor, code smell, technical debt, legacy code, cleanup, simplify, extract…
Refactoring techniques for improving code maintainability. Use when refactoring code to reduce complexity and apply SOLID principles.
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off", "fix the design", "Tailwind styling", "color palette" — from…
Refactor code to improve maintainability by consolidating redundant logic and applying DRY principles
Systematischer Prozess für sichere und effektive Refactorings mit Analyse, Planung und Verifikation.
Practical regex patterns across languages and use cases. Use when validating input (email, URL, IP), parsing log lines, extracting data from text, refactoring code with…
Use when a change to an existing system, legacy code, refactor, dependency, data contract, migration, or generated implementation needs regression risk review.
Pin every fixed bug with a test that fails before the fix and passes after, kept beside the code it guards.
Produces grounding context summaries — directory structure, recent diffs, and file patterns — from local repository state, enabling more accurate architectural and implementation…
Review repository changes for regressions and operational risks. Use when validating refactors, install scripts, or environment automation before rollout.
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue.
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
Use when completing tasks, implementing major features, or before merging to verify work meets requirements — from bg-szy/TOP-SKILLS
Use when completing tasks, implementing major features, or before merging to verify work meets requirements — from bg-szy/TOP-SKILLS
Use when completing tasks, implementing major features, or before merging to verify work meets requirements — from bg-szy/TOP-SKILLS
Request and process code reviews with proper context. Use after completing significant implementation work.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches code-reviewer subagent to review implementation a — from…
Request a high-signal Codex-backed review of a diff or task result. Use when completing tasks, implementing major features, or before merging. Codex-backed variant.
Expert semantic engineering and MBSE skill for Reqvire. Use when (1) exploring engineering knowledge graphs, (2) adding capabilities with proper ontology, requirement, an — from…
Refactors TypeScript codebases with AST-aware rename, extract, and reference finding. Use for moving functions between files, renaming across codebase, or finding all usages of a…
After a task reaches GREEN and before the quality gate commits, surface C-class refactor discoveries as structured plan-update proposals.
編輯審查規則清單（CRUD）。此 skill 只負責管理規則檔內容，不執行 code review。執行 code review 請用 /code-review:code-review。
Reviews and generates .NET/C# code following Microsoft conventions and modern patterns. Use when reviewing C# files, writing .NET code, refactoring, or when user mentions "C#",…
Revisit dashboard — one scan of everything you parked to re-check later, across every skill's memory.
Decide whether to refactor code in place or rewrite it from scratch using risk math, not frustration. Use when a component feels beyond repair and someone proposes starting over.
Runs Fable 5 and OpenAI Codex as co-founders on the Rocket Fuel operating system. Fable is the Visionary (vision, plan, standards, final review); Codex is the Integrator (filters…
Autonomous BACKLOG executor. Runs on a schedule (hourly via cron or GitHub Actions), scans BACKLOG.md for 📋 Todo items, and routes each to the appropriate skill: US-XXX →…
Specification-driven development workflow for creating requirements, design, and tasks. Use when the user wants to plan new features, fix bugs with proper specifications, refactor…
Code-quality tooling for Rails — RuboCop with rubocop-rails / rubocop-performance / rubocop-rspec / rubocop-thread_safety extensions, the rubocop-rails-omakase preset (DHH's…
Integrate RubyCritic to analyze Ruby code quality and maintain high standards throughout development.
Use when the rule set is over the Augment budget, when a new rule would breach it, or when asked to audit / merge / prune rules — runs the audit pipeline and proposes a verdict…
Trigger CodeRabbit review passes from an agent and work unresolved PR feedback threads into guided or batch autofix loops.
Use Open Code Review when an agent needs several reviewer personas to inspect a diff, debate findings, and synthesize review output before a human approves, posts, or acts on the…
Apply reusable refactoring recipes to large codebases so framework upgrades and codemods happen as auditable, reviewable changes.
Structured Autonomy Coder — lê um plano anexado (plan.md ou implementation-steps/) e implementa o código diretamente no projeto, sem gerar arquivos .md intermediários.
SaaS-dostu, multi-tenant aware kod yazım standartları. Hardcoded yasağı, tam zincir kontrolü, tenant isolation, config-driven yaklaşım.
Review a code change or PR broadly for correctness, compatibility, security, maintainability, and tests.
Safe refactoring patterns - code smell detection thresholds, baby-step refactoring, characterization tests, Expand-Migrate-Contract, Strangler Fig, primitive obsession, value…
Read-only static analysis of SAP CAP Node.js code (a Pull Request, a branch comparison, or a specific file list).
Shared fixed-fleet Workflow engine for /uberdev:uberscan (read-only audit) and /uberdev:ubersimplify (preserve-behavior refactor).
Project-specific UI refactor workflow for the Scoop news platform in /home/bender/classwork/Thesis. Use when updating Scoop frontend layouts, globe UX, research workspace, and…
Exploratory workflow for understanding problem spaces and drafting feature proposals, refactorings, or complex bug-fixes.
Analyze a problem, plan the fix, execute with verification. Use when tackling a non-trivial bug, feature, or refactor that needs structured approach.
A write-capable assistant that guides small, focused code changes end-to-end. Use when you need to make a targeted edit — add a function, fix a typo, update a config, refactor a…