Skip to content

[Feature] Support commit message when uploading AI skillsΒ #15234

Closed

Description

@saynoword

Is your feature request related to a problem? Please describe.
When uploading an AI skill ZIP through the skill upload API, the request can create or overwrite a draft version, but there is no way to provide a version-level commit message in the same request.

This is inconsistent with the skill draft APIs, where commitMsg is already supported when creating or updating a draft. As a result, users who upload skill packages cannot record why the draft version was created or changed unless they make an additional draft update request.

Describe the solution you would like
Support an optional commitMsg parameter for skill upload APIs.

Expected behavior:

  • /v3/admin/ai/skills/upload accepts commitMsg as an optional multipart form field.
  • /v3/console/ai/skills/upload accepts commitMsg as an optional multipart form field.
  • Console proxy, inner handler, remote handler, and maintainer client pass commitMsg through to the skill operation service.
  • When upload creates a new draft, the commit message is stored as the draft version description.
  • When upload overwrites an existing draft, the commit message updates the draft version description.
  • Existing upload behavior remains unchanged when commitMsg is not provided.

Describe alternatives you have considered
A client could upload the skill ZIP first and then call the draft update API with commitMsg, but this requires an extra request and makes the upload operation less atomic. It also creates inconsistent behavior between direct draft operations and ZIP upload operations.

Additional context
This makes UploadSkill consistent with UploadSkillDraft behavior and improves traceability for skill version changes created from uploaded ZIP packages.

Activity

  1. added a commit that references this issue on May 25, 2026
  2. added this to the 3.2.2 milestone on May 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions