Skip to content

Capture change proposals for a skill in Database #126

@cteyton

Description

@cteyton

Using the diff and diff --submit command, users must be able to submit change proposals to skills, including:

We must handle the following changes:

Changes linked to SKILL.md file

  • updateSkillName => Skipped. According to the Agent Skills specs, name must match the parent directory name. It means we should detect upper directory renaming or move. Which is too tricky.
  • updateSkillDescription
  • updateSkillPrompt
  • updateSkillMetadata
  • updateSkillLicense
  • updateSkillAllowedTools

Changes linked to additional file in skills

  • addSkillFile
  • updateSkillFileContent
  • updateSkillFilePermissions
  • deleteSkillFile

updateSkillFilePath is skipped so far, we'll consider it's a addSkillFile and deleteSkillFile

Example of output

Image

Note: for the moment, results are only available in the database, not in the web app.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions