Дисциплинированная реализация: код, API, schemas, configs, tests, naming, errors, reuse, sync. Используй для: реализация, доработка, рефакторинг, нейминг, реюз, контракты,…
Automatically trigger review agents after task completion. Use when strategic-planner finishes planning tasks (calls plan-consultant) or when main agent completes coding tasks in…
Implement using TDD Red-Green cycle. Focus on Red-Green only; refactoring is separate step.
Update all import statements, module references, string paths, and config references after moving or renaming files and modules.
Incrementally implement feature improvements from docs/improvements.md with tests and atomic commits. Focuses on new functionality rather than refactoring.
Improve existing agent skills based on user feedback and best practices. Use when the user wants to fix, enhance, or refactor an existing skill.
Improve test design and coverage, including TDD/red-green-refactor guidance.
Break multi-file changes into atomic commits ordered by dependency. Use for refactors, breaking API changes, or features touching 3+ files.
Use when IMPLEMENTING refactoring changes. Enforces metrics-driven protocol with before/after measurements.
Use when implementing features or refactoring with TDD - enforces writing ONE test at a time, implementing minimal code to pass, then repeating, preventing batch test writing that…
Write an infrastructure-as-code review checklist and conduct a structured review of Terraform, CloudFormation, Pulumi, or Ansible code.
JpaEntity, Adapter, Repository 클래스를 구현할 때 반드시 사용. 인프라 계층 구현 시 TDD(Red-Green-Refactor) 방식으로 진행. "JpaEntity 구현", "Adapter 구현", "Repository 구현", "영속성 계층" 작업 시 자동 발동.
Use when deciding whether similar code should be deduplicated. Prioritizes shared intent and change reason over textual similarity, avoiding harmful DRY abstractions when code…
Route ambiguous Phoenix/LiveView/Ecto work requests to the correct /phx: workflow. Use when intent is unclear, mixed (bug fix vs. refactor), or scope is ambiguous.
Human-in-the-loop code review with chunk-by-chunk approve/reject/chat loop (git add -p style). Use when reviewing PRs, diffs, patches, or documents interactively.
Guides adding and structuring internal Go packages: when to create a new package, import paths, cmd vs internal boundaries, and domain layout.
Analyze feature requests, refactor plans, or technical decisions to determine investment value and provide recommendations.
IoT quality assurance for the ESP32 pool-controller — static analysis, anti-pattern detection, code review rules, hardening for 24/7 operation, and systematic quality gates.
Guide structured analysis of problems and planning of implementation. Use when starting work on a new feature, encountering a bug, refactoring existing functionality, or any task…
对本次 diff 进行多维 code review 并自动修复，循环迭代直到收敛或达到最大轮次。 适用场景：开发完成一个 feature 或 fix 后，在提交/建 MR 前做质量保障。 触发关键词：「code review」「review 一下代码」「使用 iterative-code-review skill」 「review and fix」「做…
Systematic codebase refactor scan. Use when the user asks to scan/audit a project for refactoring opportunities — file-size violations, long functions, argument-mutation…
Design, refactor, or review code when semantic clarity is the explicit goal, using precise domain names, explicit failures and effects, useful domain types, immutable data flow,…
Z analytického kontextu (investigation.md / anomaly entry / refactor proposal) složí Jira issue body podle projektových konvencí. Předloží draft ke schválení.
Run comprehensive expert code review on current branch changes and fix findings across debug/dead code, rule violations, correctness risks, and explicit…
Improve code quality through adaptive refactoring workflows while preserving behavior and enforcing architectural standards.
Implement, refactor, or review worker-based multithreading in TypeScript/JavaScript apps (browser or Node).
Use when Code implementation and refactoring, architecturing or designing systems, process and workflow improvements, error handling and validation.
Manufacturing-fokussierter Continuous Improvement Skill fuer fabrikIQ. Implementiert Lean Manufacturing Prinzipien (5 Whys, Ishikawa, PDCA) fuer systematische Problemloes — from…
Manufacturing-fokussierter Continuous Improvement Skill fuer fabrikIQ. Implementiert Lean Manufacturing Prinzipien (5 Whys, Ishikawa, PDCA) fuer systematische Problemloes — from…
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface ass — from…
Applies Karpathy's "A Recipe for Training Neural Networks" adapted to software engineering. Forces a minimum runnable baseline before optimizing, one knob at a time, with…
Guidelines to improve coding style and avoid common pitfalls. Use when writing, reviewing, or refactoring any kind of code.
Delegate a coding task to the Kimi Code CLI (`kimi`) as a background implementer, then review its diff and land it yourself.
Auto-generate code structure index (Repo Map). Extracts class names and method signatures for component types defined in ecw.yml (e.g., Facade/BizService/Manager), grouped by…
Use after completing a refactor, implementing a major feature, or when skills may be outdated. Analyzes code changes, identifies affected skills, and proposes updates to keep team…
Use when reviewing implemented Kotlin Multiplatform / Compose Multiplatform code for architecture consistency, business-logic placement, state correctness, concurrency, Compose…
Refactor discipline for existing codebases. Enforces scope control, migration safety, compatibility, observability, and tests to keep refactors reviewable and low-risk.
Use when designing, reviewing, or refactoring module boundaries in KMP or Android projects — feature, data, app, and common modules, dependency direction, visibility control, and…
Land a large change too big for one PR as a sequence of PRs merging into a long-lived integration branch, then a final PR into main.
Post-work verification sweep run by a FRESH agent: did the change land where it actually executes, do the stated claims match disk, and what should have moved and didn't.
Reviews LangGraph code for bugs, anti-patterns, and improvements. Use when reviewing code that uses StateGraph, nodes, edges, checkpointing, or other LangGraph features.
Use when Claude Code hits "File content exceeds maximum allowed tokens" error, or when files are too large to read.
Guardrails, protocols, and operating constraints for large-scale, long-running, or parallelized AI coding tasks — migrations, codebase-wide refactors, framework upgrades, and any…
Autonomous bug-elimination loop. Iteratively invokes /bug-hunt and /implement-batch until findings converge below an operator-specified severity floor.
Autonomous technical lead. Takes commander's intent and drives a project to completion through an OODA loop over implementation, refactoring, review, and bug-hunting skills.
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.
Methodological guide for the AI Agent to safely and systematically translate, refactor, and modernize giant legacy codebases (PHP, Python 2, old React) into modern stacks.
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.