Skip to main content

Release 0.1.136

Each project can now read, edit, add and version the skills its agents and Repave IDE sessions follow, from a new Skills tab in Project Settings.

Upgrade notes​

  • Database migrations run automatically during the upgrade. They add the tables that keep skill versions; no existing data is changed.
  • .env and docker-compose.yml: nothing to edit.
  • Nothing changes for a project until someone edits a skill. A project whose skills nobody has edited keeps following each Repave release.

New​

Skills in Project Settings. The Skills tab lists every skill Repave's agents and Repave IDE sessions use. Choose one to read it, then edit it in Fields or as the whole SKILL.md, along with the reference files and scripts in its folder, and choose Save changes. The change applies to this project only, and reaches agent runs and Repave IDE sessions that start after you save. History keeps every version — each Repave release's and each one saved in the project — shows what changed from the version in use, and Use this version puts an earlier one back. Add skill adds a skill of your own, either for every agent run or as a command developers run, and Start from a folder fills it from a skill you already have. When a Repave upgrade changes a skill you edited, your version stays in use and the skill is marked, with Compare and Use Repave's version.

Improvements​

Commands you add work in Codex too. A developer command added in the Skills tab is /repave:<name> in Claude Code and /<name> in Codex. If you already have a Codex prompt or skill of your own with the same name, Repave keeps yours and the terminal says so.

repave features write-as-is-gherkin --dry-run previews an As-Is Gherkin save: it reports what the real save would refuse, and any lock it would hit, and saves nothing.