fix: skill name validation and README AI integration improvement - #5
Merged
Conversation
…tent ## Changes - Remove `_` prefix from `name:` field in all 14 SKILL.md files - VS Code skill validation only allows lowercase letters, numbers, and hyphens - Directory names retain `_` prefix for filesystem-level namespace isolation - `name:` field and directory name now intentionally differ - Restore empty `_file-output-guard/SKILL.md` content (file was blank) - Remove misplaced ````skill` code fence wrapping from `_context-ack/SKILL.md` - Update naming convention docs in `_evolution-core/SKILL.md` to reflect new rule ## Technical Details - All skill `name:` fields: `_xxx` → `xxx` (e.g., `_git-commit` → `git-commit`) - Directory structure unchanged: `.agent/skills/_git-commit/SKILL.md` etc. - Internal prose references to `_skill-name` kept as-is (they describe directory paths, not VS Code registration names) docs(readme): add AI integration one-sentence setup option ## Changes - Add "Option 3: AI Integration (One-sentence setup)" to Installation section - Provides Chinese and English one-sentence prompts for AI-assisted install - AI reads this README, understands the skill system, and runs `npx @xingyu.wang/evoskills init` --- 🤖 Generated by git-commit skill
…tall ## Changes - Remove Chinese translation from one-sentence AI integration prompt (AI assistants understand any language, dual-language was redundant) - Clarify that direct file copying is not supported and results in incomplete setup - Emphasize that CLI handles all file placement, registry generation, and content protection --- 🤖 Generated by git-commit skill
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
1 participant
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.
fix: Skill name validation fix and README AI integration improvement
Summary
This PR fixes VS Code skill validation errors caused by
_prefixes inname:fields,restores lost file content, and improves the README installation documentation.
Problem
name:values starting with_— only lowercase letters, numbers, and hyphens are allowed_file-output-guard/SKILL.mdwas accidentally emptied_context-ack/SKILL.mdhad a stray````skillcode fence wrapping the frontmatter, breaking name parsingSolution
SKILL.mdfiles: Removed_fromname:field (e.g.,_git-commit→git-commit)_prefix for filesystem-level namespace isolationname:and directory name intentionally differ: directory = filesystem isolation, name = VS Code registration_file-output-guard/SKILL.md: Restored full content from original specification_context-ack/SKILL.md: Removed misplaced````skillcode fence wrapper_evolution-core/SKILL.md: Updated naming convention docs to reflect the newname:vs directory distinctionREADME.md: Added "Option 3: AI Integration" — one-sentence prompt for AI-assisted CLI install; clarified direct file copying is unsupportedTesting
name:fields pass VS Code validation pattern (no_prefix)_file-output-guard/SKILL.mdcontent restored correctlyChecklist
name:fields use valid VS Code format_file-output-guardcontent restored_context-ackfrontmatter parsing fixed🤖 Generated by pr-creator skill