agileflow 3.3.0 → 3.4.0

package/src/core/commands/skill/delete.md

@@ -1,316 +0,0 @@
----
-description: Remove an installed skill from .claude/skills/
-argument-hint: "[<name>]"
-compact_context:
-  priority: medium
-  preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:skill:delete - Removes installed skills"
-    - "MUST list available skills if SKILL_NAME not provided"
-    - "MUST show exactly what will be deleted (tree view of files)"
-    - "MUST ask for explicit confirmation before deletion (no undo)"
-    - "MUST offer backup option before deletion"
-    - "MUST create backup in .claude/skills-backup/ if requested"
-    - "NEVER delete without explicit user confirmation"
-  state_fields:
-    - selected_skill_for_deletion
-    - backup_created
----
-
-# /agileflow:skill:delete
-
-Remove a skill from `.claude/skills/`.
-
----
-
-<!-- COMPACT_SUMMARY_START -->
-
-## 🚨 COMPACT SUMMARY - /agileflow:skill:delete IS ACTIVE
-
-**CRITICAL**: This command deletes skills with full safety features and backup options.
-
-### 🚨 RULE #1: Select Skill
-If SKILL_NAME not provided:
-```bash
-ls -d .claude/skills/*/ | xargs -I {} basename {}
-```
-Show options and ask user which to delete.
-
-### 🚨 RULE #2: Show Exactly What Will Be Deleted
-Display complete tree view:
-```
-⚠️  About to delete: skill-name
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-This will permanently remove:
-  .claude/skills/skill-name/
-  ├── SKILL.md
-  ├── references.md
-  ├── cookbook/
-  │   ├── use-case-1.md
-  │   └── use-case-2.md
-  └── .mcp.json
-
-Total: 5 files in 2 directories
-```
-
-### 🚨 RULE #3: Ask for Confirmation
-Multiple confirmation levels:
-1. **First ask**: "Are you sure?" (show file tree)
-2. **Options**:
-   - "Yes, delete permanently" - Proceed with deletion
-   - "No, keep it" - Cancel
-   - "Export first" - Create backup first
-
-### 🚨 RULE #4: Handle Backup Request
-If user chooses "Export first":
-```bash
-mkdir -p .claude/skills-backup/
-cp -r .claude/skills/<skill> .claude/skills-backup/<skill>-$(date +%Y%m%d-%H%M%S)/
-```
-Show backup location, then return to confirmation.
-
-### 🚨 RULE #5: Execute Deletion
-After confirmed deletion:
-```bash
-rm -rf .claude/skills/<skill>/
-```
-Show confirmation message with success emoji.
-
-### 🚨 RULE #6: Offer Next Actions
-After deletion, ask:
-```
-What would you like to do next?
-- Delete another skill
-- Create new skill
-- List remaining skills
-- Done
-```
-
-### Safety Features
-| Feature | Purpose |
-|---------|---------|
-| Show file tree | User sees EXACTLY what's deleted |
-| Explicit confirmation | Can't accidentally delete |
-| Backup option | Can recover if needed |
-| One at a time | No batch delete accidents |
-| Timestamp in backup | Identify which version backed up |
-
-### Backup Location
-```
-.claude/skills-backup/<skill>-<YYYYMMDD-HHMMSS>/
-```
-
-Example:
-```
-.claude/skills-backup/supabase-swift-20251227-143052/
-├── SKILL.md
-├── references.md
-├── cookbook/
-└── .mcp.json
-```
-
-### Anti-Patterns
-- ❌ DON'T delete without showing file tree
-- ❌ DON'T proceed without explicit confirmation
-- ❌ DON'T skip backup option offer
-- ❌ DON'T allow batch/wildcard deletes (one at a time)
-- ❌ DON'T delete without confirming again if backup created
-
-### REMEMBER AFTER COMPACTION
-- Delete is always: Select → Show tree → Ask confirm → [Backup if requested] → Delete → Show next actions
-- NEVER delete without explicit confirmation
-- Always offer backup option before deletion
-- Backup goes to .claude/skills-backup/ with timestamp
-- One skill at a time (no batch delete)
-
-<!-- COMPACT_SUMMARY_END -->
-
----
-
-## Workflow
-
-### STEP 1: Select skill to delete
-
-If SKILL_NAME not provided, list available skills:
-
-```bash
-ls -d .claude/skills/*/ 2>/dev/null | xargs -I {} basename {}
-```
-
-Then ask user:
-
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "Which skill would you like to delete?",
-  "header": "Select Skill",
-  "multiSelect": false,
-  "options": [
-    {"label": "<skill-1>", "description": "<description from frontmatter>"},
-    {"label": "<skill-2>", "description": "<description from frontmatter>"},
-    {"label": "<skill-3>", "description": "<description from frontmatter>"}
-  ]
-}]</parameter>
-</invoke>
-```
-
-### STEP 2: Show skill contents
-
-Display what will be deleted:
-
-```
-⚠️  About to delete: supabase-swift
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-This will permanently remove:
-  .claude/skills/supabase-swift/
-  ├── SKILL.md
-  ├── references.md
-  ├── cookbook/
-  │   ├── crud-operations.md
-  │   └── authentication.md
-  └── .mcp.json
-
-Total: 5 files in 2 directories
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-### STEP 3: Confirm deletion
-
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "Are you sure you want to delete this skill? This cannot be undone.",
-  "header": "Confirm Delete",
-  "multiSelect": false,
-  "options": [
-    {"label": "Yes, delete permanently", "description": "Remove the skill and all its files"},
-    {"label": "No, keep it", "description": "Cancel and return"},
-    {"label": "Export first", "description": "Save a backup before deleting"}
-  ]
-}]</parameter>
-</invoke>
-```
-
-### STEP 4: Handle export (if requested)
-
-If user chose "Export first":
-
-1. Create backup directory: `.claude/skills-backup/`
-2. Copy skill to backup with timestamp:
-   ```bash
-   cp -r .claude/skills/<skill> .claude/skills-backup/<skill>-$(date +%Y%m%d-%H%M%S)/
-   ```
-3. Show backup location
-4. Return to confirmation
-
-### STEP 5: Delete skill
-
-```bash
-rm -rf .claude/skills/<skill>/
-```
-
-### STEP 6: Confirm deletion
-
-```
-✅ Deleted: supabase-swift
-
-The skill has been permanently removed from .claude/skills/
-```
-
-### STEP 7: Offer next actions
-
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "What would you like to do next?",
-  "header": "Next Action",
-  "multiSelect": false,
-  "options": [
-    {"label": "Delete another skill", "description": "Remove more skills"},
-    {"label": "Create new skill", "description": "Generate a replacement skill"},
-    {"label": "List remaining skills", "description": "See what's still installed"},
-    {"label": "Done", "description": "Exit skill management"}
-  ]
-}]</parameter>
-</invoke>
-```
-
----
-
-## Backup Location
-
-Backups are stored in:
-```
-.claude/skills-backup/<skill>-<timestamp>/
-```
-
-Example:
-```
-.claude/skills-backup/supabase-swift-20251227-143052/
-├── SKILL.md
-├── references.md
-├── cookbook/
-└── .mcp.json
-```
-
----
-
-## Error Handling
-
-### Skill Not Found
-```
-❌ Skill "<name>" not found.
-
-Available skills:
-  - ui-components
-  - api-integration
-
-Use /agileflow:skill:list to see all skills.
-```
-
-### No Skills Installed
-```
-❌ No skills to delete.
-
-No skills are currently installed in .claude/skills/
-```
-
-### Delete Failed
-```
-❌ Failed to delete skill: <error message>
-
-The skill directory may be in use or have permission issues.
-Try manually: rm -rf .claude/skills/<skill>/
-```
-
----
-
-## Safety Features
-
-1. **Always confirm** - Never delete without explicit confirmation
-2. **Show contents** - Display exactly what will be removed
-3. **Export option** - Allow backup before deletion
-4. **No batch delete** - One skill at a time for safety
-
----
-
-## Usage
-
-```bash
-# Interactive mode
-/agileflow:skill:delete
-
-# Delete specific skill
-/agileflow:skill:delete supabase-swift
-```
-
----
-
-## Related Commands
-
-- `/agileflow:skill:create` - Create a new skill
-- `/agileflow:skill:list` - List all installed skills
-- `/agileflow:skill:edit` - Edit existing skill
-- `/agileflow:skill:upgrade` - Add learning capability
-- `/agileflow:skill:test` - Test skill functionality

package/src/core/commands/skill/edit.md

@@ -1,359 +0,0 @@
----
-description: Edit an existing skill's SKILL.md, cookbook entries, or references
-argument-hint: "[<name>]"
-compact_context:
-  priority: medium
-  preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:skill:edit - Modifies existing skills"
-    - "MUST list available skills if SKILL_NAME not provided"
-    - "MUST show skill structure before asking what to edit"
-    - "MUST offer special edits: rename, add cookbook, full rewrite (Plan Mode)"
-    - "MUST preview changes with diff before writing"
-    - "MUST ask for confirmation before any file writes"
-    - "For full rewrite: MUST enter Plan Mode and research before regenerating"
-  state_fields:
-    - selected_skill
-    - edit_target_file
-    - has_changes_pending
----
-
-# /agileflow:skill:edit
-
-Modify an existing skill in `.claude/skills/`.
-
----
-
-<!-- COMPACT_SUMMARY_START -->
-
-## 🚨 COMPACT SUMMARY - /agileflow:skill:edit IS ACTIVE
-
-**CRITICAL**: This command modifies existing skills with preview and confirmation.
-
-### 🚨 RULE #1: Select Skill
-If SKILL_NAME not provided:
-```bash
-ls -d .claude/skills/*/ | xargs -I {} basename {}
-```
-Show options and ask user which to edit.
-
-### 🚨 RULE #2: Show Skill Structure
-Display current skill contents before asking what to edit:
-```
-📝 Editing: skill-name
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Files:
-  1. SKILL.md (main skill file)
-  2. references.md (documentation links)
-  3. cookbook/use-case-1.md
-  4. cookbook/use-case-2.md
-  5. .mcp.json (MCP configuration)
-```
-
-### 🚨 RULE #3: Ask What to Edit
-Offer these options:
-1. **SKILL.md** - Main skill instructions
-2. **references.md** - Update documentation links
-3. **Cookbook entry** - Edit specific use-case workflow
-4. **Add new cookbook** - Create new use-case workflow
-5. **MCP configuration** - Modify MCP server settings
-6. **Rename skill** - Change skill name and folder
-
-### 🚨 RULE #4: Read Current Content
-Before editing, always read the file:
-```bash
-cat .claude/skills/<skill>/<file>
-```
-
-### 🚨 RULE #5: Preview Before Writing
-For any change:
-1. Show diff preview (- old, + new)
-2. Ask for confirmation
-3. Only write if confirmed
-
-### 🚨 RULE #6: Special Edits
-| Edit Type | Process |
-|-----------|---------|
-| Full rewrite | Enter Plan Mode, research, generate with approval |
-| Rename | Validate name, create new dir, copy files, update frontmatter, delete old |
-| Add cookbook | Create from template, update SKILL.md references |
-| Regular edits | Read → Edit → Preview → Confirm → Write |
-
-### 🚨 RULE #7: For Full Rewrite
-If user selects "Full rewrite (Recommended)":
-1. Enter Plan Mode
-2. Research web/local/codebase again
-3. Show updated plan to user
-4. Get approval
-5. Exit Plan Mode
-6. Regenerate the file with new research
-
-### Critical Edit Operations
-| Operation | Check | Action |
-|-----------|-------|--------|
-| Rename | Name is valid | Copy dir + update frontmatter + delete old |
-| Add cookbook | Template ready | Create file + update SKILL.md |
-| Change SKILL.md | Diff ready | Show preview + confirm + write |
-| Modify references.md | Links valid | Show preview + confirm + write |
-
-### Anti-Patterns
-- ❌ DON'T modify files without preview
-- ❌ DON'T skip diff confirmation
-- ❌ DON'T rename without validating new name
-- ❌ DON'T offer "full rewrite" without Plan Mode
-- ❌ DON'T leave skill in broken state (always backup before changes)
-
-### REMEMBER AFTER COMPACTION
-- Edit is always: Select → Show structure → Ask what → Read → Edit → Preview → Confirm → Write
-- Full rewrite means Plan Mode + research + approval
-- Always show diffs before writing
-- Rename requires copying and updating frontmatter
-- New cookbook entries need SKILL.md updated too
-
-<!-- COMPACT_SUMMARY_END -->
-
----
-
-## Workflow
-
-### STEP 1: Select skill to edit
-
-If SKILL_NAME not provided, list available skills:
-
-```bash
-ls -d .claude/skills/*/ 2>/dev/null | xargs -I {} basename {}
-```
-
-Then ask user:
-
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "Which skill would you like to edit?",
-  "header": "Select Skill",
-  "multiSelect": false,
-  "options": [
-    {"label": "<skill-1>", "description": "<description from frontmatter>"},
-    {"label": "<skill-2>", "description": "<description from frontmatter>"},
-    {"label": "<skill-3>", "description": "<description from frontmatter>"}
-  ]
-}]</parameter>
-</invoke>
-```
-
-### STEP 2: Show skill structure
-
-Display current skill contents:
-
-```
-📝 Editing: supabase-swift
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Files:
-  1. SKILL.md (main skill file)
-  2. references.md (documentation links)
-  3. cookbook/crud-operations.md
-  4. cookbook/authentication.md
-  5. .mcp.json (MCP configuration)
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-### STEP 3: Ask what to edit
-
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "What would you like to modify?",
-  "header": "Edit Target",
-  "multiSelect": false,
-  "options": [
-    {"label": "SKILL.md", "description": "Edit main skill instructions"},
-    {"label": "references.md", "description": "Update documentation links"},
-    {"label": "Cookbook entry", "description": "Edit a specific workflow"},
-    {"label": "Add new cookbook", "description": "Create a new workflow"},
-    {"label": "MCP configuration", "description": "Modify MCP server settings"},
-    {"label": "Rename skill", "description": "Change skill name and folder"}
-  ]
-}]</parameter>
-</invoke>
-```
-
-### STEP 4: Read current content
-
-Read the selected file:
-
-```bash
-cat .claude/skills/<skill>/<file>
-```
-
-### STEP 5: Ask for changes
-
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "How would you like to modify this file?",
-  "header": "Edit Mode",
-  "multiSelect": false,
-  "options": [
-    {"label": "Describe changes", "description": "Tell me what to change and I'll update it"},
-    {"label": "Add content", "description": "Append new sections or examples"},
-    {"label": "Replace section", "description": "Rewrite a specific section"},
-    {"label": "Full rewrite", "description": "Regenerate with research (Recommended)"},
-    {"label": "Cancel", "description": "Return without changes"}
-  ]
-}]</parameter>
-</invoke>
-```
-
-### STEP 6: Apply changes
-
-Based on user's choice:
-
-**For "Describe changes":**
-- Read current file
-- Apply user's described modifications
-- Show diff preview
-- Confirm with YES/NO
-
-**For "Full rewrite":**
-- Enter plan mode to research
-- Gather updated web docs, local docs, codebase patterns
-- Regenerate file with new research
-- Show diff preview
-- Confirm with YES/NO
-
-### STEP 7: Show diff and confirm
-
-```
-📝 Changes to SKILL.md:
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-- old line
-+ new line
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-```xml
-<invoke name="AskUserQuestion">
-<parameter name="questions">[{
-  "question": "Apply these changes?",
-  "header": "Confirm",
-  "multiSelect": false,
-  "options": [
-    {"label": "Yes, save changes", "description": "Write the updated file"},
-    {"label": "No, discard", "description": "Cancel without saving"},
-    {"label": "Edit more", "description": "Make additional changes first"}
-  ]
-}]</parameter>
-</invoke>
-```
-
-### STEP 8: Write changes
-
-If confirmed:
-1. Write updated file
-2. Show success message
-3. Offer next actions
-
----
-
-## Special Edits
-
-### Rename Skill
-
-1. Get new name from user
-2. Validate: letters, numbers, hyphens only
-3. Create new directory: `.claude/skills/<new-name>/`
-4. Copy all files
-5. Update `name:` in SKILL.md frontmatter
-6. Delete old directory
-7. Confirm completion
-
-### Add Cookbook Entry
-
-1. Ask for use case name
-2. Create `cookbook/<use-case>.md` from template
-3. Update SKILL.md to reference new cookbook
-4. Show diff and confirm
-
----
-
-## Cookbook Template
-
-```markdown
-# <Use Case Title>
-
-<Brief description of this workflow.>
-
-## Prerequisites
-
-- <Prerequisite 1>
-- <Prerequisite 2>
-
-## Instructions
-
-1. **<Step 1>**:
-   <Details>
-
-2. **<Step 2>**:
-   ```<language>
-   <code example>
-   ```
-
-3. **<Step 3>**:
-   <Details>
-
-## Example
-
-**Input**: <sample>
-**Output**: <result>
-
-## Troubleshooting
-
-- **<Problem>**: <Solution>
-```
-
----
-
-## Error Handling
-
-### Skill Not Found
-```
-❌ Skill "<name>" not found.
-
-Available skills:
-  - supabase-swift
-  - ui-components
-
-Use /agileflow:skill:list to see all skills.
-```
-
-### No Skills Installed
-```
-❌ No skills installed yet.
-
-Create a skill first: /agileflow:skill:create
-```
-
----
-
-## Usage
-
-```bash
-# Interactive mode
-/agileflow:skill:edit
-
-# Edit specific skill
-/agileflow:skill:edit supabase-swift
-```
-
----
-
-## Related Commands
-
-- `/agileflow:skill:create` - Create a new skill
-- `/agileflow:skill:list` - List all installed skills
-- `/agileflow:skill:test` - Test skill functionality
-- `/agileflow:skill:upgrade` - Add learning capability
-- `/agileflow:skill:delete` - Remove an installed skill