Multi-agent orchestration system using Claude Code's native background agents (2.0.64+) for true parallel collaboration.
Angular 20 conventions for the Alexis Trejo portfolio—standalone components, zoneless SSR, routing, services, file layout, naming, and data patterns.
Use when a Godot/.NET task needs a Layer 4 overlay completion review after a large refactor, multi-file implementation, or new feature, and the agent must assess layer boundaries,…
Spin up a PR code review sub-agent. Ranks bugs critical/high/medium/low, eliminates false positives, writes consolidated report, applies KISS/DRY fixes (main logic only, skip…
GitHub PRのレビューコメントを自動検出し、コード修正を適用する。インラインスレッド・レビュー本文・Issueコメントに対応し、CodeRabbit・Copilot等のbotコメントも処理する。PRレビュー後の修正作業を自動化したい場合に使用する。Do NOT use for レビュー自体の実施（ai-code-reviewを使用すること）。
Walk a maintainer through deep code review of open pull requests on the configured `
` repo (default: read from `/project.md → upstream_repo`).
Sweep open pull requests on the configured `
` repo (default: read from `/project.md → upstream_repo`), classify each one against the project's quality…
完整 PR 生命週期（通用版，任何專案皆可用）：從建立 PR 到 code-review → parallel review（4 個 pr-review-toolkit subagent） → fix → re-review → CI → merge。無 SDD/spectra 依賴。 SDD 專案（需要 spectra archive + Jira…
PR 作成後に Layer 1 /code-review セルフレビューを必ず実行し、指摘対応 → 自動マージまでを自律実行する。外部 AI レビュアー（Copilot/Gemini）への依頼はしない。CI・人手コメントは subscribe_pr_activity で任意監視する。対応はサイレント（ユーザー報告せず PR スレッド・Issue…
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…
Complete the required presubmit. Use before declaring a feature finished, after a large refactor or when asked.
Code review heuristics — four-axis review lens (correctness, security, design integrity, test coverage); confidence-based filtering (no finding without a concrete failure…
Design patterns — Gang of Four and beyond. Strategy, factory method, observer, decorator, adapter, facade, template method, command, repository, dependency injection.
Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading.
Refactoring discipline — Fowler's catalog of behavior-preserving moves (Extract Function, Inline Variable, Move Function, Replace Conditional with Polymorphism, Introduce…
SOLID principles — SRP, OCP, LSP, ISP, DIP (single responsibility, open-closed, Liskov substitution, interface segregation, dependency inversion).
Apply when sequencing an addition, refactor, or rewrite. Remove dead weight, redundant validators, and stub references first, then build on the simpler base.
Use when users with a CodeScene instance ask what to improve first across a project, which hotspots matter most, or how to rank refactoring candidates.
Run one PR-processing tick on the current repo's open pull requests, then stop. Finalize your own / agent-authored PRs (rebase-if-needed, /code-review then /review-fix if needed,…
Use when the user wants a Basecamp card fully implemented or continued in the current session (feature, bug, refactor, or review follow-up).
Use when writing, generating, modifying, debugging, reviewing, or refactoring code. Treat code work as rebuilding and preserving the program theory: how real-world affairs map…
Apply distilled coding principles from 14 classic software books to code review, refactoring, design, and implementation decisions.
Runs the full minerva lifecycle end-to-end for a MEDIUM change — bigger than a one-file tweak, not ambiguous or high-stakes enough for panels ("ship this with a second opinion",…
Refactor verbose or unnatural natural-language prose — code comments, test descriptions, docstrings, user-facing text — into concise, native-sounding prose in a configured target…
index.htmlのコード品質チェックとPROTOTYPE.mdとの整合性確認（自動実行）。CSS/JS/HTMLのバグ防止パターン、 フォントサイズ基準、仕様整合性を検査する。OK後はユーザーレビューへ進み、修正依頼は proto-ticket-lifecycle で管理。 パイプライン: proto-05-html-builder →…
How pwsh-code-review computes diff context using PowerShell's AST. Defines the Ring 0/Ring 1 context model, the AST index format, the call graph algorithm, and the…
How to bootstrap a PowerShell project with pwsh-code-review. Use when the user is setting up the reviewer on a new repo, when /pwsh-review-bootstrap runs, or when the existing…
How to run the deterministic static-analysis pre-pass for pwsh-code-review. Covers PSScriptAnalyzer, InjectionHunter, Gitleaks, Pester, and optional auxiliary tools.
Use when refactoring Python code, cleaning up legacy codebases, optimizing performance, enforcing type safety, or improving clean architecture in a FastAPI backend
Perform automated Python code reviews using Pylint programmatic API and pylint-json2html for report generation.
AI-powered code review for Q/kdb+ — catch bugs in the most terse language in finance
Delegate a coding task to the Qoder CLI (`qodercli`) as a background implementer, then review its diff and land it yourself.
Loads coding rules from Qodo most relevant to the current coding task by generating a semantic search query from the assignment.
Applies QML best practices when producing or working with QML source code. Use whenever QML code is the primary subject: writing, reviewing, fixing, refactoring, optimizing, or…
Provides Qwen Coder CLI delegation workflows for coding tasks using Qwen2.5-Coder and QwQ models, including English prompt formulation, execution flags, and safe result handling.
Generate Ralph-compatible prompts for single implementation tasks. Creates prompts with clear completion criteria, automatic verification, and TDD approach.
Use when designing or refactoring Snowflake RBAC: choosing a role hierarchy, creating database/schema access roles, setting up functional roles, deciding between primary and…
Readable C/C++/Rust/CUDA code rules inspired by The Art of Readable Code. Use when writing, reviewing, or refactoring C, C++, Rust, or CUDA code.
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and — from…
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and — from…
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and — from…
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and — from…
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and — from…
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and — from…
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and — from…
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and — from…
Use when designing or refactoring record types across objects with many profiles, business processes, or picklist variations.
Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green.
Analyzes a codebase scope for coupling issues, diagnoses coupling types using the Connascence framework, and proposes a comprehensive refactoring plan with concrete code changes.
Refacter code using complexity analysis and hotspot detection. Use when asked to refactor code, improve code quality, reduce complexity, or identify high-risk areas that need…
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type…
Restructure code to improve readability, maintainability, and extensibility without changing external behavior.
Use when refactoring a user-level or project-level AGENTS.md for progressive disclosure
Run cargo-coupling and similarity-rs to identify refactoring targets, then create a prioritized plan.
[Code Quality] Identifies architectural hotspots: high-churn files, coupling issues, layer violations, and dependency tangles.
Guide safe, incremental refactoring of existing code. Identify refactoring opportunities, suggest patterns, and ensure behavior is preserved through the process.
Refactor by removing backward compatibility and legacy layers. Use when modernizing APIs, cleaning up migration debt, removing compat shims, or eliminating stale feature flags.
Use when modernizing APIs, removing compat shims, killing feature flags, or rewriting a subsystem cleanly.
코드베이스 대상으로 "분석 → 리팩터 → 테스트 → 리뷰" 4단계 체인을 실행하는 스킬. /refactor-chain {target-path} 명령어 입력 시 반드시 이 스킬을 사용한다. 각 단계는 독립 서브에이전트로 실행되며, 이전 단계 결과가 다음 단계 프롬프트에 주입된다.