Renames opaque identifiers and aligns nearby prose while preserving code behavior.
npx skills add https://github.com/Yassimba/loom --skill clarify-code-yassimba
Please help me install this Agent Skill. Skill: clarify-code Source: https://github.com/Yassimba/loom/tree/main/skills/clarify-code Command: npx skills add https://github.com/Yassimba/loom --skill clarify-code-yassimba
proc, tmp2, or handleIt do in a billing module. Run this Skill on that module to rename each identifier after the concept it holds, verify old names are gone, and pass the repository's required checks. ## Quick Start Use the clarify-code skill to rename the opaque identifiers in this module so a first-time reader understands it, without changing any behavior.High-intent search queries and answers about installing and using this skill.
Rename at the owning definition, then update every caller, test, type annotation, and relevant document. Build a rename map first so each change has a known blast radius, then run the focused checks and the repository's required gate to confirm behavior is preserved.
Classify each identifier as precise, opaque, or contract, then rename opaque names using the project's domain vocabulary so each name reveals the concept at its use site. Align nearby docstrings and comments with the new vocabulary and remove stale claims.
Contract names such as storage, wire, CLI, environment, and public API identifiers should be preserved by default. Change them only when explicitly requested, and add a compatibility alias only when compatibility is requested.
Avoid folding design problems into a clarity pass; keep existing abstractions, control flow, validation, and error behavior in place and report design issues separately. Also skip renaming when identifiers are already precise at their use sites.
Search for every old name to confirm none remain, run the focused checks covering the changed seams, then run the repository's required gate. Finally read the diff cold to confirm each new name reveals its concept without relying on the rename map.
tuantiensiuGuide developers through the red-green-refactor cycle for test-driven development.
rodrigo-altissimoAnalyze code complexity and propose deep-module refactoring steps.
icepengAnalyze repository structure to standardize issue tracker, triage labels, and documentation layout.
tiendungchsGuides reframing of hard design and debugging problems before committing to solutions.