bac2b27bb8
BREAKING CHANGES: - Remove -cskill suffix from all skill names (use standard kebab-case) - Simplify marketplace.json to only official fields (fixes Issue #5) - SKILL.md body must be <500 lines (progressive disclosure via references/) New features: - Cross-platform support for 8+ platforms (Claude Code, Copilot, Cursor, Windsurf, Cline, Codex CLI, Gemini CLI) - scripts/install-template.sh: Auto-detect platform installer with --dry-run - scripts/validate.py: Spec compliance checker for generated skills - scripts/security_scan.py: Security scanner for hardcoded keys and dangerous patterns - MIGRATION.md: v3.x to v4.0 migration guide - 6 new reference files for progressive disclosure from lean SKILL.md Key changes: - SKILL.md: 4,116 → 272 lines with spec-compliant YAML frontmatter - marketplace.json: Stripped to {name, plugins} only - article-to-prototype-cskill/ → article-to-prototype/ - stock-analyzer-cskill/ → stock-analyzer/ - Export system integrates validation + security scanning - README.md rewritten for all supported platforms - Phase 5 pipeline outputs SKILL.md-first, spec-compliant skills Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
30 lines
1.1 KiB
Markdown
30 lines
1.1 KiB
Markdown
# SC-045: Directory Renamed When It Doesn't Match Name Field
|
|
|
|
> Covers: FR-002, Edge case 2.3 — Directory name doesn't match name field: rename directory to match, warn user
|
|
> Type: Edge Case
|
|
|
|
## Given
|
|
- During migration or manual editing, a skill directory is named `old-name/`
|
|
- The SKILL.md inside has `name: new-name` in frontmatter
|
|
|
|
## When
|
|
- The "Migrate Legacy Skill" flow is invoked on `old-name/`
|
|
|
|
## Then
|
|
- The directory is renamed from `old-name/` to `new-name/`
|
|
- The user is warned about the rename
|
|
- All files inside are preserved after the rename
|
|
- Validation passes after the rename
|
|
|
|
## Verification Method
|
|
|
|
**Method**: CLI command
|
|
|
|
**Steps**:
|
|
1. Create `old-name/` with SKILL.md containing `name: new-name`
|
|
2. Run the migration flow on `old-name/`
|
|
3. Assert `old-name/` no longer exists
|
|
4. Assert `new-name/` exists with all original files
|
|
5. Run validation on `new-name/` and assert it passes
|
|
|
|
**Expected evidence**: `old-name/` is gone. `new-name/` exists with intact files. Validation passes. Output includes "Renamed directory from 'old-name' to 'new-name'".
|