Pipeline skill — turns a URL or DESIGN.md into a concrete UI structure with decisions already made. Extracts live design tokens, normalizes them into a semantic system, applies UX…
Review code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md workflow compliance.
Review full-stack code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md compliance.
Review static site code for bugs, security issues, performance problems, accessibility gaps, and CLAUDE.md compliance.
Refresh stale or drifting learnings and pattern docs in docs/solutions/ by reviewing, updating, consolidating, replacing, or deleting them against the current codebase.
Get git records for specified users and days, perform code review for each commit, and generate detailed code review reports
Review code changes by analyzing git diffs, leaving inline comments on PRs, and performing thorough pre-push review.
Review GitHub PRs with surgical precision. Flag only high-severity issues (bugs, security, performance, breaking changes) via succinct inline comments on specific lines.
Manages all git operations (commit, push, branch management, PR creation) in a standardized, safe, and consistent way.
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: \"Rename this function\", \"Extract this into a module\", \"Refactor this c — from…
Review a code change (diff or PR) for ship-readiness before merge. Use when reviewing your own or someone else's changes prior to committing/merging/etc.
Use GliderMCP for C#/.NET navigation, diagnostics, references, call graphs, impact analysis, and safe refactoring.
code-reviewer 에이전트를 통해 코드 품질과 아키텍처를 검사하는 스킬. 레이어 경계 검증, 통신 패턴 검사, 코드 품질 이슈 식별. 특정 파일/디렉토리 경로를 지정하거나 인자 없이 현재 브랜치 변경 파일 자동 감지.
Review Go code in this project against the standard quality bar — formatting, vet, idiomatic style, error handling, concurrency, and testing.
Comprehensive code review checklist for Go projects. Evaluates code quality, idiomatic patterns, error handling, naming, package structure, and test coverage.
Review Go code with a defect-first approach using repository policy (constitution.md first, then AGENTS.md fallback).
Planificación de features y tareas en Go. Usar al iniciar una nueva feature, diseñar APIs, o planificar refactorizaciones.
Organize Go packages by domain with internal boundaries, consumer-side interfaces, and structure that grows on demand.
Safe refactoring agent. First documents all inbound surfaces (HTTP, gRPC, message queues, etc.), creates exhaustive e2e tests with testcontainers to lock behavior, then plans and…
Safe refactoring workflow for Go: behavior-preserving steps, compiler-checked renames, extracting packages, breaking circular dependencies, and strangler migrations — always…
Write and refactor SQL query code using Mike's go-sqlparams package. Use when building parameterized SQL, constructing WHERE clauses, pagination/sorting, or binding named params.
Use when creating, modifying, reviewing, or refactoring Go production code, especially API shape, package boundaries, naming, dependency ownership, error handling, concurrency,…
Use when reviewing GDScript or C# Godot code — checklist of best practices, common anti-patterns, and Godot-specific pitfalls
Use when Godot project has code-created objects, tight coupling via direct references, monolithic scripts over 150 lines, or needs scene-first architecture with signals and…
Capture the current output of untested legacy code as a recorded baseline so a refactor can prove it changed nothing.
Go language server (gopls) providing code intelligence, refactoring, and analysis for .go files. Use when working with Go code that needs autocomplete, go-to-definition, find…
Plan and execute safe refactoring using dependency analysis — find dead code, preview renames, verify no critical paths broken.
Search and rewrite code with GritQL — declarative queries backed by tree-sitter. Use when refactoring across languages or applying AST transformations at scale.
Searches and rewrites codebases using GritQL declarative queries. Use when refactoring across languages, migrating dependencies, enforcing code patterns, or applying complex…
Delegate a coding task to the Grok Build CLI as a background implementer, then review its diff and land it yourself.
Ground every version, stack, and best-practice choice in what is current today, read from the release channel rather than from recall.
Review changed files for bugs, security issues, and code quality; produce REVIEW.md — from alo-exp/silver-bullet
When planning or refactoring an outbound motion, validating account selection before investing pipeline resources, debugging why a sequence is unde...
Use when refactoring unhealthy code and needing Code Health findings to choose small safe steps and verify improvement.
Rename, split, merge, or restructure an existing canonical artifact with cross-reference scrubbing and an explicit rename-map deliverable.
Hope-native review of uncommitted, staged, commit, branch, or PR changes: discover concrete regressions, independently verify candidates, and report actionable findings first…
Hope-native baseline for implementing, fixing, refactoring, and maintaining code: inspect the repository first, protect user changes, keep scope narrow, and finish with direct…
Use after design or implementation to package handoff notes, refactor UI code, split god components, document tokens, and prepare maintainable frontend deliverables.
Audits a project's agentic harness (CLAUDE.md, AGENTS.md, .claude/rules, .claude/settings.json) and refactors it into a layered, path-scoped configuration that loads only what is…
Build, refactor, and debug Hawk pages, templates, cards, and Hawk-500 code. Use when working with Hawk's page/file/card/load model, Sail/manx UI, `%twin`/`%call`/`%view`/`%lens`…
Use when writing, refactoring, or deciding how to test an HDL module, component, or IP block (ROHD, Chisel, SpinalHDL, Verilog, VHDL) and you need it parameterized, validated, and…
Review PRs, branches, diffs, and workflow artifacts for package-level go/no-go readiness with severity-ranked synthesis.
Reviews HealthKit code for authorization patterns, query usage, background delivery, and data type handling.
Perform a large-scale refactor with staged work and validation; use when changes span many files or modules.
Apply the Honest Code principles when writing, reviewing or refactoring code. Use when writing new code, reviewing a diff, refactoring, or when the user asks to make code…
Use when writing or refactoring code, before creating files - enforces separation of pure business logic (Functional Core) from side effects (Imperative Shell) using FCIS pattern…
Reviews a GitHub pull request like a thoughtful human reviewer and writes the feedback to a markdown file.
Run a full architectural refactor cycle — explores the codebase for friction, categorizes dependencies, designs competing approaches for structural changes, then fixes everything…
Run Codex's native code-review on the current branch, working tree, or a specific commit. Use when the user invokes /hyperclaude:hyper-code-review, or after producing code changes…
Use when applying Hyperflow's orchestration doctrine in Codex, Antigravity, or another single-agent surface.
Hyperflow execution phase. Use when a task file exists in .hyperflow/tasks/ and the work needs building — verbs like build, implement, add, refactor, "wire up", "run the plan",…
Structured code reviews with severity-ranked findings and deep multi-agent mode. Use when performing a code review, auditing code quality, or critiquing PRs, MRs, or diffs.
Process code review feedback critically: check correctness before acting, push back on incorrect suggestions, no performative agreement.
Simplifies, polishes, and declutters code without changing behavior. Use when asked to simplify, clean up, refactor, declutter, remove dead code or AI slop, or improve re — from…
Refactor IC10 code for clarity and structure. Use when user wants to reorganize code, apply design patterns, improve naming, or make code more maintainable without changing…
Analyze system-wide impact of changes before making them. Use before modifying shared utilities, changing APIs, or refactoring core functionality.
Use when implementation is complete and ready for verification, before marking task done. Absorbs code-reviewer role — no separate code review needed in ECW workflow.
Full-lifecycle project workflow. Takes batched tickets, implements via /implement-batch, runs smoke tests, then executes a comprehensive quality pipeline (refactor, review-arch,…
Execute refactoring tasks from a task file with parallel agent orchestration
Autonomous TDD build agent. Implements a plan using red-green-refactor with BDD scenarios as RED tests.