بِسْمِ ٱللَّهِ ٱلرَّحْمَـٰنِ ٱلرَّحِيمِ
AI
How an AI coding agent uses refac, and where to get the refac skill for it.
refac is built for agents that work without an IDE. This section covers the part that connects the two: the refac skill, a folder of instructions that tells your agent when to use refac and how.
What the skill gives your agent
The skill is one folder, refac-cli, in the refac repository on GitHub. Its entry file, SKILL.md, tells the agent which tasks are a job for refac (moving or renaming files, folders, modules, and symbols), the commands to run, what each language supports, and what --project-path means in each language. Longer material sits next to it in references/ and is read only when a task needs it: installing the language tools, Kotlin, how each language behaves, and how to wire an agent harness.
The skill loads when a task fits it and stays out of the way otherwise. There is no server to run and no MCP configuration. The binary also documents itself: refac <command> --help and refac guide hold the in-depth topics, and the skill tells the agent to read them instead of guessing.
What you need besides the skill
The skill teaches the agent to use refac. It does not contain refac. Install the binary first (Installation), then put the skill where your agent looks (Get the skills). When a move fails because a language server is missing, the skill sends the agent to refac doctor <language>, which prints what to install.