Autonomous comprehensive refactoring. Three-phase pipeline — Phase 1 /refactor (tactical, loops internally to convergence) → Phase 2 loop of /review-arch + /implement-batch until…
Interactive LeetCode-style teacher for technical interview preparation. Generates coding playgrounds with real product challenges, teaches patterns and techniques, supports…
Expert system for identifying deprecated patterns, suggesting refactoring to modern standards (Python 3.12+, ES2024+), checking test coverage, and leveraging AI-powered tools.
Investigate unfamiliar legacy code before edits. Triggers: legacy module, unknown repo, risky refactor, trace ownership. Triggers:
Refactor legacy codebases, migrate outdated frameworks, and implement gradual modernization. Handles technical debt, dependency updates, and backward compatibility.
Knowledge steward for Johnny-Decimal/Zettelkasten Obsidian vaults. Use when managing vault structure, auditing links, cleaning up notes, constructing new vault sections, reviewing…
Secure code review skill for application risk analysis, threat modeling, scanner tuning, and developer-focused remediation guidance.
Apply linuxlewis's code review style to pull requests, local diffs, or proposed code changes. Use when asked to review code the way linuxlewis would, emulate Sam Bolgert's review…
Nightly direct-execution skill for reducing code complexity thresholds. Receives pre-computed threshold data, refactors violations, updates thresholds, commits, and creat — from…
Analyzes source code repositories using list-codes and ghq. Use this when the user asks to analyze, review, explain, or refactor a codebase (local or remote).
Reviews Phoenix LiveView code for lifecycle patterns, assigns/streams usage, components, and security. Use when reviewing LiveView modules, .heex templates, or LiveComponents.
Worker that checks DRY/KISS/YAGNI/architecture compliance with quantitative Code Quality Score. Validates architectural decisions via MCP Ref: (1) Optimality - is chosen approach…
Checks DRY/KISS/YAGNI/architecture compliance with quantitative Code Quality Score. Use when implementation tasks are Done and need quality scoring.
Auto-fixes low-risk tech debt (unused imports, dead code, commented-out code) with >=90% confidence. Use when audit findings need safe automated cleanup.
Audit code comments and docstrings quality across 6 categories (WHY-not-WHAT, Density, Forbidden Content, Docstrings, Actuality, Legacy).
Logic optimization and image-based code tasks with Codex CLI in --yolo mode. Use when (1) optimizing code logic or algorithms, (2) processing image inputs (screenshots, diagrams,…
Run multi-axis implementation review through Loom critique. Use before merge, after feature or bug-fix implementation, when receiving review feedback, when reviewing AI/human…
Use when a code diff, branch, PR, worker output, or implementation-complete ticket needs a code-focused quality review across correctness, tests, architecture, security,…
Implement changes in small verified slices. Use when a feature, refactor, migration, or bug fix touches multiple files, feels too large to land at once, needs feature flags, or…
Run Ralph implementation packets. Use for larger feature, refactor, test, migration, or cleanup slices when a Ralph-ready ticket needs fresh context, explicit write scope,…
Maintain bounded execution and acceptance. Use when adding or changing code, tests, docs, config, refactors, migrations, cleanup, blockers, evidence/review disposition, or any…
Lorekeeper-specific BLOCKER patterns, severity tiers, and review checklist — used when reviewing any PR touching src/lorekeeper/
Reviews Rust macro code for hygiene issues, fragment misuse, compile-time impact, and procedural macro patterns.
Review code changes against requirements for production readiness. Evaluate technically, no rubber stamping.
Write a comprehensive plan to refactor with TDD tasks. Every step has real code, no placeholders.
Use to sequence your work on a change — make it work, then make it right, then make it fast, in that order; keep one concern per change; don't tangle a feature with a refactor.
Analyzes existing code and guides new type design to make invalid states unrepresentable using type system techniques such as sum types, newtypes, typestate, branded types, and…
Finds oversized files, binary bloat, and accidental artifact commits in a repo — large files currently tracked, large blobs hiding in git history, LFS migration candidates, asset…
Aide à identifier, prioriser et planifier le remboursement de la dette technique avec des métriques de suivi.
Help users manage technical debt strategically. Use when someone is dealing with legacy code, planning refactoring work, deciding between rewrites vs.
Pre-publication manuscript audit producing a section-level refactoring report with citation hygiene and submission-readiness checks.
重构 workflow。用于模块拆分、迁移、rename、baseline+regression 验证。 触发词：refactor, 重构, 拆分, 迁移, extract, rename module, map-refactor. Requires MAP .review/ infrastructure. Merge gate enabled.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and — from…
Code review conventions for all projects. Covers mandatory review requirements, review scope, PR sizing, reviewer and author responsibilities, and automated review integration.
Pre-refactor context loading -- queries Pensyve memory for past decisions, failures, and patterns related to a refactoring target, then compiles a briefing.
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "rename this function", "extract this into a module", "split this class", " — from…
Use to declare a structural intent BEFORE editing in a fleet — what symbols you'll touch and why — so other agents on your branch coordinate around you.
Generates, reviews, and fixes Mermaid-only sequence diagrams following syntax rules and best practices.
Drives deterministic code red-green-refactor. Use before writing or changing any implementation file — write a failing test first, watch it fail, write minimal code to pa — from…
Review metravel diffs for correctness, project-rule compliance, validation gaps, and residual risk. Use when Codex needs a focused reviewer pass before handoff, approval, or…
Design the small details — triggers, rules, feedback, loops and modes — that separate good products from great ones.
Create, update, refactor, explain, or review Microsoft Agent Framework solutions using shared guidance plus language-specific references for .NET and Python.
Choose, review, or refactor project profiles that map mise tools to ecosystem-specific reference sets.
Use when CUDA Tile or tile-shaped GPU refactors need Mission Control planning, validation, and benchmark discipline.
Run a safe Mission Control refactor workflow. Use when the user wants non-trivial refactors that need codebase understanding, snapshots, path locks, contracts, validation…
Request a Mission Control snapshot or restore point before risky work. Use when the user wants rollback safety before refactors, broad edits, or uncertain changes, preferably…
Execute migration to Mistral AI from OpenAI, Anthropic, or other providers. Use when migrating to Mistral AI from another provider, performing major refactoring, or re-platforming…
Multi-frontier-model mob review of someone ELSE's PR — review-only, never modifies their code. 自動偵測 codex / agy，≥1 家即啟動 R1 獨立 + R2 交叉 debate + aggregate，產出彙整 review 報告 並（經確認後）貼回…
Use when asked to audit a module, check its health, or assess whether it should be refactored. Runs structural query, risk check, and test generation automatically.
Use when after rewriting or refactoring a Python module (such as calculate_feature_overlap.py
Use Morfx when Codex needs deterministic AST-based code queries, replacements, staged edits, or recipe-driven refactors through the Morfx MCP server instead of brittle text-only…
Tech Lead and Architect. Use for architectural decisions, design guidance, task planning, code quality, and refactoring strategy.
Run a structured pre-merge review across correctness, readability, architecture, security, and performance instead of relying on a shallow spot check.
Stage ④.h verify sub-workflow — 4-specialist Agent Team Pattern C 多维度审查 (关键发布 / 大重构 PR 升级, code-review + gstack-review + gstack-cso + gstack-qa 4 teammate 互相 SendMessage 质询, NOT…
Expert guidelines to refactor legacy PHP codebases into clean, modern, and scalable MVC-structured projects / Pedoman ahli untuk merefaktor codebase PHP lama menjadi proyek…
Reviews HealthKit code for authorization patterns, query usage, background delivery, and data type handling.
Reviews Combine framework code for memory leaks, operator misuse, and error handling. Use when reviewing code with import Combine, AnyPublisher, @Published, PassthroughSu — from…
Manufacturing-fokussierter Continuous Improvement Skill fuer fabrikIQ. Implementiert Lean Manufacturing Prinzipien (5 Whys, Ishikawa, PDCA) fuer systematische Problemloes — from…
Detect naming conventions from existing code, then audit new or all symbols for violations. Reports inconsistencies across files without enforcing a single style.
Create native modules with sequential native-bridge-builder then code-reviewer agents