Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a chan — from…
Iterative auto-fix code review — runs `/optimus:code-review` in a fresh subagent context per iteration, applies fixes, runs tests, bisects failures, and continues until…
Use this skill when conducting or improving code reviews. Provides structured review processes, conventional comments patterns, language-specific checklists, and feedback…
Use when reviewing code changes for quality, security, performance, or maintainability issues and identifying simplification opportunities in a single token-efficient pass
Breaker（Claude）× Judge（Codex）の二者構造で、反例生成とテスト実行により「本当の欠陥」のみを抽出する敵対的コードレビュー。重要変更・最終ゲート・見逃したくない場面に使う。対象が PR なら確認ゲート経由で PR にレビューを投稿する。通常のレビューは /code-reviewer を使うこと。
Author, update, and validate prompts (skills, agents, subagents, workflows, commands, rules, templates, or just any generic prompt).
Use when docs/solutions/ learnings may be stale — after refactors, migrations, or dependency upgrades, when a retrieved learning feels outdated or contradicts a recently solved…
Prove a change achieved its intended outcome: a mechanical build+test+lint prerequisite (delegated to /toolchain:check and /toolchain:lint, STOPs if broken), then outcome…
Read-only GitHub activity card for a named contributor on . Fetches PR authorship, code-review activity, issues, and PR/issue comments over a configurable window.
Use when: designing, reviewing, or refactoring C++ error handling policy, exceptions vs std::expected vs error codes, exception safety guarantees (basic, strong, nothrow), RAII…
Create a ralph (a deterministic execution plan with steps) for a coding task. Use when the user wants to plan and break down a feature, bug fix, or refactor into executable steps…
Record a technical-debt item (DEBT-NNN) — registration only by default, or register + auto-generate a fix TASK with --task.
Systematic codebase quality scan for identifying duplication, redundancy, and improvement opportunities.
Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a chan — from…
Perform holistic review of completed refactoring, validate improvements, and create follow-up tasks if needed
Reviews a Pull Request or validates local changes before opening a PR, following the eventaservo architecture and Rails patterns. Analyzes committed, staged, and unstaged changes.
Snapshot a Figma frame's metadata, tokens, design-context, and screenshot to local files under `.ai-docs/figma//` so downstream agents (design-builder, design-grader, spec…
Systematically fix all failing tests after business logic changes or refactoring
Use when assessing overall project quality, onboarding onto a new codebase, or before major refactoring to establish a baseline.
Write less code and say less about it. Applies YAGNI and stdlib/native-first so the agent writes the minimum code that needs to exist, and responds tersely — stripping filler,…
Keep a software system cheaply changeable over its whole life — the phase that is 60–80% of total cost and most under-resourced — across: classifying and funding it, making…
Lightweight implementation orchestrator for low-complexity work — fixes, refactors, doc changes, or single-AC features that do not warrant a phase plan or factory decomposition.
Use when the sensei tutor selects or applies a pedagogical framework. Routes to 10 frameworks: 5w2h (default — structured analysis), pear-loop (Plan-Explore-Analyze-Rewrite),…
Facilitates deliberate skill development during AI-assisted coding. Offers interactive learning exercises after architectural work (new files, schema changes, refactors).
Run a standalone code review on lilnas changes — correctness, testing, maintainability, project standards — plus conditional reviewers (kieran- typescript, julik-frontend-races,…
Narrow bare `rescue _ ->` / `rescue e ->` so UndefinedFunctionError, KeyError, and typos propagate instead of being swallowed.
Orchestrates a same-series Odoo git rebase - replaying a feature or fix branch onto an updated base of the SAME Odoo major version - forwarding INTENT, not diff text.
Use when starting a new feature, refactor, or multi-step task - before writing any code. Use especially when scope is unclear or multiple files are involved.
Use when the user wants a new feature or capability built and it is not a one-to-two-step change - "I want to add X", "let's build a way to Y", "can we add", "new feature: Z", a…
Create a clean PR branch by filtering out .design/ and .planning/ commits. Code-review-ready branch for the design implementation work.
Use when: deciding whether a pull request, diff, or change set is too large or mixed to review in one pass, splitting an oversized PR into reviewable slices, separating refactor…
Synthesize a recurring code-review rule into a custom lint rule — gated by an independent soundness test that abstains rather than ship a checker it can't prove sound
Generate synthetic code context for LLM coding tasks. Automatically use this before making code changes, fixing bugs, refactoring, or answering questions about the codebase.
Review my code, code review, is this ready to ship, check for bugs, security audit, review this PR, pre-merge check, is this safe to deploy, check code quality.
Detect duplicate Rust code using AST-based similarity analysis. Use when working with .rs files and looking for code duplication or refactoring opportunities.
Safety analysis before refactoring -- dependency graph, test coverage, public API exposure, blast radius verdict.
Create a detailed refactor plan with tiny commits via user interview, then file as a GitHub issue RFC.
Use when: planning or executing a behavior-preserving refactor: characterization coverage before touching code, small reversible steps with a green check after each, strict…
Atomic rename of Python symbols (functions, classes, methods) or modules using the structural index. Finds all static callers, import sites, __all__ re-exports, and Sphinx…
Use when: sharpening a software requirement or a requirement set so it is buildable and decidable rather than merely well-formed - replacing vague quality words and quantifiers…
Triage reviewer comments on a GitHub PR with receiving-code-review discipline — verify each against the codebase, then accept/push-back/clarify, and optionally reply in-thread.
Polish the active feature before review — code polish always; UI normalize + ship-quality pass when UI is touched.
Mine your Claude Code sessions and code-review history for the corrections you keep repeating, cluster them, adversarially verify each candidate, and distill the survivors into…
Use when writing or refactoring Go collection/pointer helper code in OpenMeter, especially when choosing between standard library slices/maps helpers and github.com/samber/lo for…
Function-level refactor workflow using call graph tools (Epic 114). Use before changing a symbol's signature, deleting a function, or refactoring callers — maps blast radius via…
Thoughtbox-first Theseus workflow for behavior-preserving refactors. Use this when structure changes but behavior must stay fixed and scope drift needs hard boundaries.
Create, update, review, or refactor VS Code Copilot skills, hooks, and MCP configs. Use when the user wants to build or maintain reusable skills, lifecycle hooks, MCP…
Generate a PR description from the current branch's changes against a GitHub PR, using the gh CLI. Use when writing, drafting, or updating pull request descriptions, PR summaries,…
Run comprehensive code quality checks, tests, and fixes autonomously
Functionality Isolation Protocol — analyze dependencies for a file or symbol to understand the blast radius of changes.
Refactoring guidance with design patterns and code improvement strategies.
Parallel 3-reviewer code review: Security, Business-Logic, Architecture.
Scan the codebase for common code smells using threshold-based detection: long methods, god classes, long parameter lists, deep nesting, magic numbers, data clumps, and more.
This skill should be used when the user asks to "refactor context file", "split CLAUDE.md into skills/rules/hooks", "AGENTS.mdを分解", "コンテキストファイルを整理", or wants a single context file…
Executes automated project-wide refactoring with a focus on cross-file optimization. This skill should be used when the user asks for project-wide refactoring, cross-file…
This skill should be used when the user asks to "review ruby code", "audit ruby codebase", "find over-engineering in ruby", "simplify ruby classes", "review lib/", or wants to…
This skill should be used when the user asks to "clean my code", "make it human readable", "make this readable", "rewrite this cleanly", "refactor this", "clean up this function",…
This skill should be used for SB-owned refactoring: evaluate scope, preserve behavior with baseline tests, make structural changes, and prove nothing regressed.
4-phase code review: UNDERSTAND, VERIFY, ASSESS risks, DOCUMENT findings.
Use this skill when the task involves creating, reviewing, or refactoring installable skills, shared skill references, or reusable agent-authoring guidance; when the work depends…