This skill should be used when reviewing pull requests, performing comprehensive code review, analyzing code changes before merge, or when the user asks for…
Use this skill when orchestrating multi-agent adversarial code reviews using Claude Code agent teams.
Automate migration between Kotlin/Android dependency injection frameworks. Covers Hilt → Koin, Dagger → Koin, Toothpick → Koin, Kodein → Koin, Koin 3.x → Koin 4.x upgrades, Koin…
Use this skill whenever the user wants to create, refactor, restyle, compare, validate, or export draw.io / DrawAI diagrams.
This skill should be used when the user asks about Effect-TS patterns, services, layers, error handling, service composition, or writing/refactoring code that imports from…
Use this skill on every programming task — writing code, fixing bugs, refactoring, explaining code, running tools, or answering technical questions.
Create detailed implementation plans for software features and refactoring tasks. Use this skill when planning new features, architectural changes, or major refactoring efforts.
Performs a comprehensive pull request review covering bugs, project conventions, test quality, and architecture.
Use this skill whenever writing, reviewing, or refactoring Go code that uses the fp-go library (github.com/IBM/fp-go/v2).
Use this skill to review code. It supports both local changes (staged or working tree) — from iice257/Skills-quickstarter-essentials
Write clean, consistent code following naming conventions, DRY principles, small focused functions, automated formatting, and meaningful variable names.
Good Night, Have Fun. Make ONE provably-correct, complexity-reducing change on a fresh branch off the default branch, then stop.
Use this skill when building, reviewing, or refactoring Go code that must follow strict design discipline — ATDD/TDD workflow, explicit dependency injection, package-boundary…
This skill should be used when the user asks to "create a skill", "audit this skill", "refactor skills", "doctor agent skills", "check skill quality", "fix frontmatter", "skill…
Refactor Scala code and apply good practices from 2020 Hindsight Scala (https://2020-hindsight-scala.kevinly.dev/docs/).
TDD（RED→GREEN→REFACTOR）でフェーズ単位の新機能実装やバグ修正を行う。docs/TODO.md があるとフェーズ管理し、なければ単独タスクとしてサイクルを回す。テストファーストを厳格に遵守。「実装したい」「TDDで実装」「機能を追加」「バグを修正」などで起動。
This skill should be used when reducing the cognitive complexity threshold of the codebase. It lowers the threshold by 2, identifies functions that exceed the new limit, generates…
This skill should be used when reducing the maximum class/module lines threshold and fixing all violations.
This skill should be used when reducing the maximum lines per method threshold and fixing all violations.
Use this skill when the user asks for iterative self-review, repeated fix-and-recheck cycles, post-review remediation, or to keep reviewing until no issues remain.
Audit, diagnose, and explain a Jeedom 4.5 home automation install in a read-only way. Use this skill whenever the user asks about an existing Jeedom installation — diagnosing…
Autonomous programming mode for openclaw.ai. Use this skill whenever a user requests any code change, feature addition, refactor, bug fix, or project task —...
ALWAYS apply this skill for ANY software development task. Triggers: implement, create, build, add, write, code, function, class, component, API, feature, fix, bug, debug,…
Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss process improvements.
Review an open GitHub pull request or the current local branch and working tree with parallel, independent reviewers and evidence-based validation.
Build and modify Phoenix LiveView code using current LiveView patterns. Use this skill whenever the user asks for LiveView pages, components, forms, events, navigation, streams,…
Expertise in LLVM tooling development including Clang plugins, LLDB debugger extensions, Clangd/LSP, and LibTooling.
This skill should be used whenever the user wants to log time after the fact in Lucen Track — phrases like "log 2h on X", "I worked 90 minutes on the billing refactor yesterday",…
Use for ANY rename, file-move, or move-symbol refactor — especially rename-heavy work across multiple files.
This skill should be used when the user asks to "review this PR/MR", "review this merge request", "review this module", "audit this module before merge", "review this theme",…
Intelligent skill router that analyzes user requests and automatically dispatches to the most appropriate skill(s) or zen-mcp tools.
Use when the user is working with a multi-repo **workspace directory** (a parent dir holding several cloned repos side by side) and wants routine multi-repo git or shell…
Use this skill when performing manual memory consolidation (Dream-equivalent). Reviews, consolidates, and prunes memory files under ~/.claude/projects/*/memory/.
Use this skill when the user asks for a code review, audit, PR/diff review, bug risk scan, security/performance/style feedback, or validation of recent changes.
Use this skill when building, debugging, refactoring, or reviewing ASP.NET Core MVC apps with Razor views, controllers, ViewModels, validation, Tag Helpers, View Componen — from…
Use this skill when the user asks to design, implement, refactor, or review custom ASP.NET Core Tag Helpers in C#, including TagBuilder usage, strongly typed attributes,…
Delegation mode for open-code-review (OCR). Instead of OCR calling an LLM endpoint, this skill instructs the host agent to perform the code review itself, using OCR only for…
Run an overnight autonomous workflow that takes a cluster of related GitHub issues (typically a P1 review-panel finding set) and ships them to merged PRs by morning.
Run a parallel code review across multiple local CLI coding agents (codex, claude, opencode) and synthesize their findings.
Enforces modern Python 3.11+ coding standards, PEP 8 compliance, and type-hinting best practices automatically.
TypeScript conventions and patterns for any TypeScript code in the Phoenix monorepo — including js/packages/, app/, and any other TS directories.
Create a detailed refactor plan with tiny commits via user interview. Writes the plan to a local REFACTOR_PLAN_.md file.
Use this skill to walk through an existing code base and fix surface-level problems that are obvious on a careful read: typos, grammar mistakes in comments and strings,…
This skill should be used when the user asks to review a GitHub pull request AND post the findings as a comment on the PR ('review and comment on PR', 'review PR roi comment len…
Use this skill to keep Jetpack Compose state alive across HotSwan hot reloads by understanding the three escalating tiers Compose HotSwan uses (tier 1 targeted recomposition, tier…
This skill should be used only when the user explicitly asks to use `$ralph-specum-refactor`, or explicitly asks Ralph Specum in Codex to revise spec artifacts after impl — from…
Use this skill whenever someone is planning, scoping, or proposing what to build. This includes: describing a new feature or system they want to create, listing requirements or…
Refactor existing code for readability and maintainability - naming, function size, nesting depth, duplication, comments, error handling and test clarity - without changing…
Comprehensive catalog of 60+ refactoring techniques for Java code based on Martin Fowler's "Refactoring" and Alexander Shvets' "Refactoring Guru".
Finds the largest TypeScript files in the Mini Infra codebase, helps the user pick one, explores how it's wired into the rest of the app, proposes a DRY refactor strategy,…
Use this skill when the user says 'refactor', 'refactoring plan', 'code cleanup', 'reduce duplication', 'simplify code', 'tech debt', 'god class', 'tight coupling', or needs to…
Use this skill when a file exceeds ~350 lines (target) / approaches the 500-line hard cap, or has mixed responsibilities (UI + Logic + Types).
This skill should be used when the user asks to "analyze code for refactoring", "produce a refactoring plan", "code refactoring review", "refactor analysis", "find code smells",…
Use this skill when refactoring code to improve readability, reduce duplication, or simplify complex logic.
Use this skill when designing or refactoring emergency operations UI in React with a modern clean visual language, semantic rescue colors, and fast task-oriented navigation.
MUST be used FIRST, before any other tool, for EVERY user request that mentions a specific tool, API, file format, service, framework, library, CLI, platform, dataset, or — from…
Verify code changes are clean before considering a task done. Use this skill after making any code change — bug fix, feature, refactor.
This skill should be used when users request code review, refactoring, or code quality improvements for Ruby codebases.
This skill SHOULD be used when the user asks to "review code", "find dead code", "check for duplication", "simplify the codebase", "find refactoring opportunities", "do code…
Use this skill whenever the user asks to add a feature, fix a bug, refactor code, or write tests. Forces a discipline of writing test scenarios in markdown BEFORE coding, mapping…