Skip to main content
Version: 0.1.148

Skills

Skills are the written instructions 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. Repave ships the skills its agents need, and they work in every project without anything to set up. Your team adds its own on top: the way this project names its endpoints, writes its release notes or resolves its lint.

Open Skills under Management in the project sidebar to add and edit your project's own skills. The page lists only the skills your project added; Repave's skills are not shown there and can't be changed, though your agents and Repave IDE sessions keep using them. The list is grouped by who uses the skill:

  • 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.

Your skills apply to this project only; other projects don't see them.

If your project has no skills yet, the page opens on Add a skill.

Type in Filter skills, at the top of the list, to narrow it to the skills whose name or description contains what you type.

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.

You can also ask the project assistant to write or change one of your skills for you: it shows you the draft, and saves it only when you click Save skill. In the Repave IDE, ask Claude Code or Codex the same way: it writes the skill and saves it for you with repave skills save, under your name, and your open sessions use it straight away. If someone saved the same skill after it read it, the save is refused rather than overwriting their version. Neither can change one of Repave's skills: they add one of your own instead.

Who can change skills​

Everyone on the project can open the Skills page and read your project's skills, 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 that start after you save, and its Repave IDE sessions that are already open — there is no need to restart the IDE. Agents already running keep the text they started with. In an open session, a new Claude Code or Codex conversation has your version straight away. A Claude Code conversation that was already open is told on the developer's next message which skills changed, and asked to run /reload-plugins to use them; Codex picks up the change on its own. 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) that none of Repave's skills already has, 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.

Remove skill removes one: it is listed under Removed, no agent or session gets it, and Restore skill brings it back with its history.

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 skill's copy is kept — the whole folder, not only SKILL.md — 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.

Changes made by Repave learning​

When a change Repave learning suggested is adopted, by someone on the Learning page or by Repave itself in Auto-adopt, it is written into this project's skills. A change can also adjust one of Repave's own skills for this project, including the steps Repave's implementation agents follow on every run; that change is not shown on the Skills page. One of your skills it changed says so above its editor: Repave learning changed this skill, with the lesson it learned, and Not yet proven until Repave can check that the change helps. View lesson opens the lesson on the Learning page, with the changes it was learned from. Compare shows what it changed. Undo puts the version it changed back in use (for a skill it added, it removes the skill, unless someone has edited it since), and Repave does not make that change again. Repave never overwrites an edit someone made: if a skill changes after Repave suggested a change to it, the suggestion is outdated and Repave suggests it again on top of that edit. In History these versions are labelled Repave learning, with the lesson as their note.

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