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.
Refactoriser une fonction JavaScript pour améliorer sa lisibilité, sa maintenabilité et sa testabilité. À utiliser pour réorganiser un code sans en changer le comportement.
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.
House style for answering code review feedback: every reviewer point quoted verbatim with the reply beneath it, consolidated into one comment.
Review one document from its file path, such as a design draft on disk or a document with uncommitted edits, or the documents a pull request changes, through the code-review…
Analyze structured code-review findings and open flags for an explicit date range and repository set, and recommend guidance, reviewer, and analyzer changes.
Implement one unit of work end-to-end — from a tracker issue OR an ad-hoc description: spec review, TDD (RED→GREEN→REFACTOR), pre-PR self-review, open a PR, then drive the…
Polish the active feature before review — code polish always; UI normalize + ship-quality pass when UI is touched.
Code review of redis_queued_locks changes against the project's own invariants and conventions (WATCH/MULTI lock safety, read/write key families, the lock index superset invariant…
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,…
ตั้งค่าและใช้งาน ast-grep สำหรับ code search, lint และ refactoring ด้วย AST-based patterns — dispatcher เข้า workflows/{scan,rewrite,transform,migration}
Break a work-items.md file (produced by /plan-work-items) into independently-grabbable GitHub issues, one per slice, in each slice's target repo.
Perform a standards-based code review on a GitHub Pull Request, then post the findings as inline review comments and mark the PR as 'Requested changes'.
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.
Author a new Claude Code skill the house way, or refactor a fat skill into a lean SKILL.md + references/.
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…
Review 3D Gaussian Splatting implementation code for correctness, performance bugs, and best practices.
[52] EXECUTE. Three-stage refactoring workflow: (1) iterative research of refactor/modularization options, (2) plan + risk/edge-case analysis + Scope150 validation, then implement…
5W1H Decision Framework Tool. Use for: (1) Systematic decision-making before creating todos, (2) Preventing duplicate implementation, (3) Detecting avoidance behavior, (4)…
Author and validate A12 Kernel document models with the dmtool CLI — both a model's structure (fields, groups, type definitions, includes, config) and its validation rules.
Multi-dimensional code assessment across security, quality, performance, and maintainability with confidence-gated reporting (>=80%) and Router Contract generation.
Pre-release ABAP code security and quality peer review across 12 dimensions. Auto-runs abaplint + ATC.
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, designing systems, or making architectural — from…
AI-native software development lifecycle that replaces traditional SDLC. Triggers on "plan and build", "break this into tasks", "build this feature end-to-end", "sprint p — from…
Use when a Godot/.NET task needs a Layer 4 overlay review to prevent abstraction decay during feature work, flow extension, or touched-code refactoring, especially around flag…
Detects code smells in PHP codebases. Identifies God Class, Feature Envy, Data Clumps, Long Parameter List, Long Method, Primitive Obsession, Message Chains, Inappropriate…
Map the access surface of a feature a software engineer is about to ship. Use when the engineer names a specific feature or PR and wants a structured read of who can reach what,…
Use when a bug is reported, something is broken, or asked to debug or fix specific behavior. Ends with the fix proven by a test that fails before and passes after.
Review JusticeHub code against ACT ecosystem values. Enforces cultural protocols, ALMA principles, and regenerative design.
Use when something is reported as slow or asked to speed up a named page, query or endpoint. Ends with that one part measurably faster, shown by numbers from before and after a…
Use when asked to refactor, clean up or restructure existing code without changing what it does. Works in small steps with tests after each one, after stating goal and scope and…
Use when creating or refactoring Action Mailer emails. Applies Rails 7.1+ conventions, parameterized mailers, preview workflows, background delivery, and email design best…
GitHub Actions workflow authoring conventions for readable, least-privilege workflows — .github/workflows/*.yaml layout, explicit scoped triggers, boolean logic with truthy/falsey…
Use when creating or refactoring Active Job background jobs. Applies Rails 8 conventions, Solid Queue patterns, error handling, retry strategies, and job design best practices.
Code review: IoC, RESTful, Contracts, Security (OWASP), Clean Architecture, SOLID.
Use when a task needs structural/relational code navigation — call graph, references, blast-radius, trace flows, safe refactors — and the GitNexus plugin is enabled.
Use when allocating feature/hotfix/refactor/chore/docs IDs or creating branches — canonical `[NNNN][L]` format that the scripts (next-id.sh, get-branch-metadata.sh, done.sh) expect
RED-GREEN-REFACTOR execution discipline for AI agents. Use when implementing any feature or bugfix that has (or should have) tests — forces a failing test confirmed for the right…
Address code review feedback by walking through comments one at a time with the user. Use when the user has received code review comments — on a GitHub PR, in a document in the…
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human.
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it shoul — from…