Skills

Skills are the written instructions Repave's agents and Repave IDE sessions follow to do each kind of work — how a feature file is written, how step definitions are bound, how lint is resolved. Open Skills under Management in the project sidebar to see every one, in two groups:

• Agents and developers — every agent run is offered these, and developers can use them in the Repave IDE.
• Developers — commands a developer runs in the Repave IDE, such as committing or starting UAT.

A change here applies to this project only. Every other project keeps Repave's version, and a project nobody has edited follows each Repave release as it always has.

Type in Filter skills, at the top of the list, to narrow it to the skills whose name or description contains what you type. The description searched is the one this project uses, so a skill you edited is found by its new words.

Choose a skill to read it. Each skill has two copies, Claude Code and Codex, because the Repave IDE runs either assistant; agent runs use the Claude Code copy. Each copy is edited and versioned on its own.

A skill is a folder: its SKILL.md and any files beside it — reference notes an agent reads, scripts it runs, schemas. The editor shows the folder beside the text, and every file in it can be opened and edited.

Who can change skills

Everyone on the project can open the Skills page and read every skill, both copies and their history. Only someone who can edit the project — its owner and editors — sees Add skill, Save changes, Use this version and the other controls that change a skill; anyone else reads the page without them, and Edit reads View.

Editing a skill

Edit the text in place and choose Save changes. You can edit in Fields — the description, which is what an agent reads when deciding whether to load the skill, and the instructions — or in SKILL.md, the whole file. Switch between them at any time without losing what you typed. A skill's name and audience cannot be changed, because agents' instructions refer to skills by name.

Files. In the editor's file list, New file adds a file at the path you type, such as references/notes.md — folders are made as you name them. Upload adds a folder, or files and .zip archives; loose files go into the folder of the file you have open. Each file and folder has a ⋯ menu to Rename it (a folder takes everything in it along) and, for a folder, Remove folder. Remove file is above an open file. A file that starts with #! is a script agents and developers can run. Skills hold text files only, up to 1 MB in all; a file that is not text is refused by name. Every change to the files is saved with Save changes, as one version with the rest of the skill.

Add a note if you like; it is shown in the history beside your version.

Your version reaches this project's agent runs and Repave IDE sessions that start after you save. Agents already running keep the text they started with. Choosing another skill with unsaved changes asks before discarding them.

If someone else changed the skill after you opened it, saving is refused so neither change is lost silently: choose Reload to see theirs.

Adding a skill of your own

Add skill, at the top of the list, adds a skill to this project only. Give it a name (lowercase letters, numbers and hyphens), who uses it, a description and instructions:

• Agents and developers — offered to every agent run in this project, which loads it when its description fits the work, so write the description as what the skill is for and when to use it. Developers can use it in the Repave IDE too.
• Developers — a command developers run in this project's Repave IDE sessions: /repave:<name> in Claude Code, /<name> in Codex.

To bring a skill you already have — a folder with a SKILL.md, written for Claude Code elsewhere — choose Start from a folder and pick the folder or a .zip of it: the form is filled from its SKILL.md, and its other files are added with it. Adding makes both the Claude Code and the Codex copy; edit either afterwards. The name and who uses it can't be changed once it is added.

Your own skills are marked ADDED in the list. Remove skill removes one: it is listed under Removed, no agent or session gets it, and Restore skill brings it back with its history. Repave's own skills can't be removed.

If a later Repave release ships a skill with the same name as one you added, yours stays in use and the skill says so, with Compare and Use Repave's version.

History

Every version of a copy this project can use is kept — the whole folder, not only SKILL.md: the ones each Repave release ships, labelled with the release, and every one saved in this project, labelled with who saved it, when, and their note. Versions saved in other projects are not shown. History lists them, newest first, with In use on the one this project's agents get. Choose a version to see Changes from the version in use, file by file, or its Full text, and Use this version to put it back in use. Nothing is ever deleted while the project exists, so this can always be undone the same way.

When Repave updates a skill you edited

Upgrading does not replace your edits. When a release changes a skill whose copy is on this project's version, that version stays in use, the skill is marked in the list, and the copy says which release changed it. Compare shows what the release changed; Use Repave's version puts it in use.

The one exception is a release that changes who a skill is for — turning a developer command into a skill every agent is offered, or the reverse. Your version was written for the old audience, so Repave's version goes into use and yours stays in the history. For the same reason, Use this version refuses a version written for a different audience than the release has the skill for.

A copy on one of Repave's versions — including an older one you went back to — follows Repave's releases: the next release that changes it puts the new text in use. Going back to an earlier release does the same in reverse: copies that follow Repave's releases return to that release's text, and copies on this project's version keep it.

On an installation that runs agents as Kubernetes pods, those agent runs use the skills built into the release, not edited versions.