docs: add Skills workflow guidance to CLAUDE.md#78
Closed
ondrejhlavacek wants to merge 1 commit into
Closed
Conversation
Consolidate skill-related guidance under a unified ## Skills section. Adds a Skills Workflow note reminding contributors that publishing requires a manifest version bump and that skill renames need explicit user approval. Existing Skill Script Path Conventions become a sibling subsection.
tomasfejfar
requested changes
May 25, 2026
|
|
||
| ### Skills Workflow | ||
|
|
||
| - When creating or modifying skills in the AI kit, remember publishing requires a version bump in the skill manifest. Don't rename skills without explicit user approval. |
Contributor
There was a problem hiding this comment.
Duplicate
- Bump the version in the plugin's
.claude-plugin/plugin.json- Bump the version in
.claude-plugin/marketplace.jsonfor the corresponding plugin entry
Member
Author
There was a problem hiding this comment.
But it never worked for me unless explicitly told.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the repo-level CLAUDE.md to codify skills publishing workflow guidance for future Claude Code sessions, while preserving the existing script path conventions under a unified ## Skills section.
Changes:
- Adds a new
## Skillssection with a### Skills Workflowsubsection describing publishing/versioning and renaming expectations. - Nests the existing “Skill Script Path Conventions” content under
### Script Path Conventions(content preserved).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| ### Skills Workflow | ||
|
|
||
| - When creating or modifying skills in the AI kit, remember publishing requires a version bump in the skill manifest. Don't rename skills without explicit user approval. |
|
|
||
| ### Skills Workflow | ||
|
|
||
| - When creating or modifying skills in the AI kit, remember publishing requires a version bump in the skill manifest. Don't rename skills without explicit user approval. |
|
|
||
| ### Skills Workflow | ||
|
|
||
| - When creating or modifying skills in the AI kit, remember publishing requires a version bump in the skill manifest. Don't rename skills without explicit user approval. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release Notes
Documentation-only change. No runtime impact.
Plans for customer communication
None.
Impact analysis
Updates the repo-level
CLAUDE.mdso future Claude Code sessions know the AI kit's skill publishing rules:Existing
Skill Script Path Conventionscontent is preserved verbatim, now nested as### Script Path Conventionsunder a unified## Skillsparent. No behavior change for any plugin or skill.Change type
Docs.
Justification
Codifies feedback that has been recurring in sessions — keeps the rule discoverable next time someone (or Claude) touches a skill.
Deployment
Merge & automatic deploy.
Rollback plan
Revert of this PR.
Post release support plan
None.