Make install command non-destructive with merge support

[ibrahimkteish]

Summary

• Remove destructive file deletion from install command
• Add support for installing to current directory with --path .
• Add path validation for ALL custom paths to ensure they contain /skills
• Add helpful error messages with usage examples when validation fails
• Add user confirmation prompt for custom path installs
• Fix extraction to place skills directly in target path (not in nested skills/skills/ folder)
• All install operations now merge files instead of replacing

Motivation

Previously, pfw install would delete everything in the target directory before installing, which could cause loss of custom or work-in-progress skills. Additionally, users could accidentally install to arbitrary locations like /tmp or project root directories. Finally, the zip extraction was creating a nested skills/skills/ structure instead of placing skills directly in the target path.

This change makes the install command always merge new files with existing ones, validates that installations only happen in appropriate skills directories, and correctly extracts skills to the target location.

Changes

1. Non-destructive by default: Removed FileManager.default.removeItem() call for the install directory - installations now preserve existing files (individual skills are still updated to latest versions)
2. Current directory support: Users can now use --path . to install into their current working directory
3. Flexible path validation: Any --path argument is validated to ensure it contains /skills (supports various naming conventions like .copilot, .claude, .github, .config, etc.)
4. Improved error messages: Clear, helpful error messages with examples when path validation fails
5. User confirmation: Prompts for confirmation before installing to any custom path
6. Correct extraction: Skills are extracted directly to the target path, not into a nested skills/ subfolder
7. Updated help text: Documents the new current directory option

Examples

Valid usage:

# Default install to ~/.claude/skills/the-point-free-way
pfw install --tool claude

# Install to custom project path (any directory structure containing /skills)
pfw install --tool claude --path /Users/me/MyProject/.claude/skills
pfw install --tool claude --path /Users/me/MyProject/.github/skills
pfw install --tool claude --path /Users/me/MyProject/.config/skills

# Install to current directory (must contain /skills in path)
cd ~/.claude/skills/my-custom-skills
pfw install --tool claude --path .

Invalid usage (now properly rejected):

# Will show helpful error message
pfw install --tool claude --path /tmp
pfw install --tool claude --path /Users/me/MyProject

Test plan

• Test default install: pfw install - should merge into default location
• Test valid custom path: pfw install --path /project/.claude/skills - should prompt and merge, skills directly in path
• Test invalid custom path: pfw install --path /tmp - should error with helpful message
• Test current directory in valid location: cd ~/.claude/skills/test && pfw install --path . - should prompt and merge
• Test current directory in invalid location: cd /tmp && pfw install --path . - should error with helpful message
• Verify existing files are preserved and skills are placed directly in target (not in nested skills/ folder)
• All 20 unit tests pass

[johankool]

Some suggestions. Not saying it's up to you to fix them, just sharing what I found when trying to use pfw with copilot-cli.

[ibrahimkteish]

closing in favor of a better implementation here #3