yandex / yandex/implicits

plugin.json: add explicit version; reconsider skill name

Open
#62 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Swift
Stars
43
Forks
5
PR merge metrics
No merged PRs in 30d

Description

1. Add an explicit version to plugin.json

There's no version today. When it's omitted, Claude Code versions the plugin by its git commit SHA — fine for git-based marketplace installs, but when the plugin ships as part of the released Swift package there's no git context, so no SHA. Then the Claude Code plugin cache (~/.claude/plugins/cache) can't tell versions apart and autoUpdate has nothing to compare. Set an explicit version at release, matching the package version.

2. Skill name doubles under the plugin namespace

Claude Code renders plugin skills as plugin:skill → here implicits:implicits-usage-guide. One name can't be both clean under that render and self-descriptive when surfaced bare:

  • (a) rename → usage-guideimplicits:usage-guide (clean); but bare usage-guide is ambiguous if the skill is ever surfaced outside the implicits: prefix.
  • (b) keep implicits-usage-guide; self-contained, but the render stays doubled.

Gate: is the skill ever surfaced without the implicits: plugin prefix? No → (a), yes → (b).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading plugin.json and the Swift package's release/version metadata, then verify how the skill is surfaced with and without the implicits: prefix. Done means plugin.json carries the release version and the skill name follows the outcome of that check; the issue names no test file or command.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
release, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.