refactoring-safely
Refactors code in small, test-backed steps without changing behavior. Use when refactoring, improving structure, or when the user asks to refactor safely.
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-19 00:15
41,769 results
Refactors code in small, test-backed steps without changing behavior. Use when refactoring, improving structure, or when the user asks to refactor safely.
Writes tests before implementation using red-green-refactor. Use when implementing features or bugfixes, or when the user asks for TDD.
Examine the user on a change or document an agent produced, before they merge, ship or sign off, so they own it instead of rubber-stamping it. Takes their…
Use when a Grok Bot needs OpenCode as compute (implementation, QA, verification) and must pick box vs the user's Mac, start visible titled sessions, steer them…
Select authorized PR reviewers, assign one request owner, and reuse substantive review coverage.
Use for "interrogate", "adversarial review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". One Astra xhigh Judge…
Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at…
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust…
Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime…
Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence…
Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data…
Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that…
Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of…
Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving…
Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller…
Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states…
Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of…
Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one…
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a…
Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.
Expert Senior Backend Engineer (Polyglot). Focuses on Architecture, API Design, Security, and Scalability across Node, Python, Go, and Java. Strictly follows…
Expert Blockchain Engineer (10+ Years). Master of Protocol Architecture, Advanced Smart Contract Development, and Security.
Diagnoses dbt Cloud/platform job failures by analyzing run logs, querying the Admin API, reviewing git history, and investigating data issues. Use when a dbt…
Use when adding or moving code across shared/frontend/backend modules in packages/kilo-jetbrains/ — split-mode RPC contracts, serialization classloader…