Skip to content
DOCS

Use Emendant from a coding agent

A coding agent that upgrades an SDK from memory can write calls that the new release changed or removed. The /emendant skill makes the agent run Emendant instead, and show you what Emendant reports.

The skill is in a public repository, Emendant/emendant-skill. It adds no network request of its own. It runs the same npx emendant commands that you can run yourself.

What the agent does

Section titled “What the agent does”

When you ask the agent to upgrade a covered SDK, it does these steps:

  1. It runs emendant scan and shows you the report as Emendant printed it.
  2. For each change that Emendant does not patch, it runs emendant explain <change-id>, edits the reported places from that guidance, and says that Emendant did not verify the edit.
  3. It runs emendant fix. Emendant proves its patches in a copy of your repository, together with the edits from step 2, and gives each patch a grade: test verified, typechecked or structurally checked.
  4. With your agreement, it upgrades the dependency and applies the patches.
  5. It runs emendant scan --adopted again, then your typecheck and tests.
  6. It ends with a table of each change, its grade, who made the edit, and the change’s page on SDK Changes.

After the agent writes new SDK code, ask it to check that code. It runs emendant scan --adopted, which finds calls from an older SDK version that the installed version changed or removed.

The agent does not add --allow-host-run, --allow-registry-credential, --model-provider or --no-verify unless you ask for them.

Install

Section titled “Install”

Claude Code

Section titled “Claude Code”
/plugin marketplace add Emendant/emendant-skill
/plugin install emendant@emendant

Run it with /emendant:emendant, or ask Claude to upgrade a covered SDK. To get /emendant in one repository, copy the skill into it:

Terminal window
mkdir -p .claude/skills/emendant
curl -fsSL https://raw.githubusercontent.com/Emendant/emendant-skill/main/skills/emendant/SKILL.md -o .claude/skills/emendant/SKILL.md

Codex

Section titled “Codex”
Terminal window
codex plugin marketplace add Emendant/emendant-skill
codex plugin add emendant@emendant

Run it with $emendant. Codex runs commands in its own sandbox, and Emendant cannot start its sandbox inside it. So inside Codex, fix grades its patches structurally checked only. Run npx emendant fix in your own terminal to get the typechecked or test verified grade.

Cursor

Section titled “Cursor”
Terminal window
mkdir -p .cursor/skills/emendant
curl -fsSL https://raw.githubusercontent.com/Emendant/emendant-skill/main/skills/emendant/SKILL.md -o .cursor/skills/emendant/SKILL.md

Windsurf

Section titled “Windsurf”
Terminal window
mkdir -p .windsurf/workflows
curl -fsSL https://raw.githubusercontent.com/Emendant/emendant-skill/main/windsurf/workflows/emendant.md -o .windsurf/workflows/emendant.md

Run it with /emendant.

What the skill does not change

Section titled “What the skill does not change”

Emendant reports only the changes in its feed. A clean scan is not a full review of an upgrade. If your typecheck fails at a place Emendant did not report, the agent says that Emendant has no entry for it. Any edit the agent makes there is its own, not Emendant’s.