Frontend 코드 리뷰. PR의 프론트엔드 코드를 컴포넌트 설계, 상태 관리, 렌더링 성능, 접근성 관점으로 분석. 사용법: /review-frontend
Plans review acquisition systems, customer prompts, timing, and response frameworks. Use when the user asks to generate more reviews or improve review quality.
Run the Julia code review protocol on Julia scripts. Checks code quality, type stability, parallel computing patterns, and scientific computing standards.
Use when reviewing a weekly learning sheet for pedagogical quality — evaluates beginner motivation, intuition, example quality, and proof correctness
Comprehensive review of local uncommitted changes using specialized agents with code improvement suggestions
Interactive code review as a panel discussion: an implementer agent defends decisions while a reviewer surfaces findings, with specialist reviewers added based on what the diff…
\"Search, review, and manage workflow memories — patterns, decisions, lessons, strategies. 搜索、審查、管理工作流記憶：模式、決策、教訓、策略.
Review auto-memory for the current project. Shows accumulated learnings, identifies noise, and helps promote permanent patterns to CLAUDE.md, rules, or skills.
Review code changes for Effect-TS pattern compliance in the Reactive Agents framework. Use when reviewing PRs, completed packages, or any code changes to enforce project…
実装完了後に、確定プラン (finalize-plan 出力)、または DD 該当タスクを転記した簡易プランと実装後の diff を突き合わせ、実装漏れ・仕様逸脱・計画外差異を検出したいときに使用する。「プランと突き合わせて」「実装漏れがないか見て」「diffがプラン通りか確認して」等の依頼で起動する。実案件 dogfood (2026-07-06)…
CODESYS ST 코드 리뷰. PR의 PLC 코드를 Infrastructure 아키텍처, 네이밍 규칙, 시퀀스 데드락, 모듈화 관점으로 분석. 사용법: /review-plc
Fetch PR review comments, validate each against the actual code, auto-fix obvious issues, and escalate genuine design decisions. Leaves all changes in the working tree.
Simulated peer review panel for manuscript prose. Spins discipline-specific agents for multi-perspective review.
Review a PR, branch or file path and recommend the highest ROI improvement opportunities. TRIGGER when the user asks if the code is ready, looks good, or is otherwise complete.
Run the R code review protocol on R scripts. Checks code quality, reproducibility, domain correctness, and professional standards. Produces a report without editing files.
Проверка документа ревью кода на соответствие стандарту — frontmatter, именование, секции Контекст ревью и Итерации, вердикт, статус OPEN/RESOLVED.
This skill reviews Dapr Workflow activity implementations for idempotency, retries, error boundaries, and convention violations.
This skill reviews Dapr Workflow code for non-determinism hazards that would cause stuck workflows on replay.
This skill reviews the HTTP management endpoints (start, status, terminate, pause, resume, raise-event, purge) that an app exposes for Dapr Workflows.
Enable the code review stop hook in .reviewer/settings.local.json. Optionally takes a shell expression for when to enforce (defaults to always).
Given an open issue or PR, scores the project's configured reviewer roster across three signals — touched-area eligibility, git-history familiarity with the changed paths, and…
Reviews GitHub pull requests for the Medusa repository. Checks PR template compliance, contribution guidelines, code conventions, and community contribution limits.
Revisão de código abrangente: qualidade + compliance + segurança. Classifica achados por severidade. Combina revisão de código genérica com validação de domínio regulado.
Analyse, redesign, or complete a GridPonder level. Reads the level JSON, evaluates design quality (aha moment, difficulty, gold path validity, cheap alternatives), then proposes…
Revisa contratos mercantiles contra el playbook del despacho e identifica desviaciones — from betobetico/claude-para-abogados
Revisione approfondita contratto B2B italiano: commessa, SLA, penale, limitazione responsabilità, foro, 1341-1342, IP, recesso, DPA. Nessuna consulenza legale.
Revisione contratto di nomina responsabile (art. 28 GDPR) term-by-term: istruzioni, sub-responsabile, misure, breach, audit, trasferimenti.
Revisione approfondita licenziamento: qualificazione (giusta causa, giustificato motivo), procedimento, art. 18, impugnazione, prove. Output memo e checklist rischi.
Revisione NDA / accordo riservatezza B2B italiano: definizioni, scopo, durata, carve-out, legge applicabile, rimedi. Nessuna consulenza legale.
Restart a live agent with new generation. Use when the user says "revive", "restart live agent", or wants to refresh a live agent's session.
Proveďte revizi smlouvy oproti vyjednávacímu playbooku vaší organizace — označte odchylky, vygenerujte návrhy úprav (redlines) a poskytněte analýzu obchodních dopadů.
Evaluates returned RFQ/RFP responses against the original ask using weighted scoring, total cost of ownership modeling, and supplier risk flags.
Ricerca giuridica su fonti italiane e UE: normativa, prassi e giurisprudenza in ogni materia (civile, penale, amministrativo, lavoro, tributario e specialistiche).
Preflight health check for a rig project: detect things that make rig degrade or fail — missing gh auth or the project scope, an unreachable board, an invalid config, no CI gates,…
Plan and run a multi-ticket epic: decompose a feature into parent + child items and stack PRs on a shared integration branch instead of landing each on main.
Create, view, move, or manage tickets in the project's issue tracker (Linear, GitHub Issues, or none).
Local code review, both halves. `find` (default): walk the REVIEWER.md catalog + scope invariants against a diff, two adversarial passes, return triaged P0–P3 findings —…
Run post-merge code cleanup: audit recent changes for dead code, duplicates, and stale comments, then safely remove them.
Manage isolated git worktrees: create one wired up for dev (fetch, branch from base, symlink env, install deps), list them with PR state, or safely remove merged ones.
Construction 단계 실행 직전, Inception 아티팩트와 설계 문서를 교차 분석하여 12개 카테고리 기반 위험 체크포인트를 탐지한다. 비즈니스 연속성·보안·외부 통합·데이터 일관성·비용·성능·규제·가용성·장애 전파 반경·운영 복잡도·의존성 취약점·롤백 가능성을 각각 PASS/WARN/BLOCK으로 판정하고…
Workflow completo per richieste interessato GDPR (artt. 15-22): classificazione, verifica identità, mappatura sistemi, esenzioni, bozza lettera e log decisioni.
DevRites menu + router. Without args, renders the menu. With a verb (e.g. `spec`, `build`, `review`), dispatches to the matching `rite-` skill — `/rite spec foo` is…
Adopt an existing or legacy codebase into DevRites by reverse-engineering current behavior, seeding conventions, and establishing the workflow.
Run the entire DevRites lifecycle end-to-end with no per-phase human iteration — spec → define → build×N → prove → polish → review → seal → ship — choosing the best option at…
Converge intent and live code. Use when resuming a half-built feature, after `/rite-adopt` drift, or the user asks "what's left to build". Not for initial planning.
Decompose an approved `spec.md` into `plan.md` + vertical task slices + `state.md`; every acceptance criterion maps to ≥1 slice.
Doctor DevRites setup or index health. Use when workflow wiring is broken, the user asks to check DevRites, or says "reindex". Not for application bugs.
User-invoked explainer that teaches one concept, diff, idea, or recent-work recap with an optional retrieval check-in.
Frame an ad-hoc ask before coding, then audit the diff. Use for underspecified imperative asks, raw-diff self-audits, or `/rite-quick` setup. Not a lifecycle gate.
Compact the current chat into a handoff doc a fresh agent can pick up cold — syncs chat-only context into the canonical `.devrites/` files, references artifacts by path.
User-invoked review of the learning ledger; promotes recurring lessons to project rules or principles.
Reshape an active plan — decompose / reslice / repair / reorder / split FE-BE / unblock — without changing product behavior unless asked.
Project-grounded verdict for adopting, switching, rejecting, or revisiting a named external technology, library, platform, CVE, or pattern.
Prove the completed feature — full tests + build + typecheck + lint + browser-proof ladder — walking `spec.md` acceptance criteria one by one.
Resolve open `questions.md` entries on the active feature — answer one, drop one, or batch-resolve from a file — and clear `state.md` `Awaiting human` so the workflow resumes.
Final GO / NO-GO gate — walk `spec.md` acceptance against `evidence.md`, fan out reviewers in parallel, block on Critical, ask y/N on Important, demand type-GO before irreversible…
Ship the sealed feature and close the task — render type-GO, run the irreversible git commit/push/tag (or open the PR), write ship.md, then archive the workspace and clear…
Investigate a new feature and write `spec.md` (placement, gaps, design refs, measurable acceptance) under `.devrites/work//`.
Read-only report on the active feature — phase, active slice, next action, evidence, open questions, drift, risks, handoff readiness.
Temper a readied spec before planning. Use when the user says "temper this", "strategy review", "pre-mortem the spec", or asks if we are over/under-building.