feat: add symlink script for Git submodule usage#64
Conversation
pbakaus
left a comment
There was a problem hiding this comment.
Thanks for your contribution! I have one suggestion that I think would make this much easier for adoption, otherwise looks promising.
| echo "Linking .$PROVIDER to parent directory..." | ||
|
|
||
| # Check if target already exists in parent | ||
| if [ -e "$PARENT_DIR/$PROVIDER_DIR" ]; then |
There was a problem hiding this comment.
I'm assuming that a lot of people will already have e.g. a .claude folder, so this technique wouldn't work then...would it not be better to symlink the sub folders (.claude/skills/{folders in here})?
|
Good catch — updated the script so it now creates symlinks only inside the provider's skills folder (e.g. |
Hey @pbakaus @amirgeek ran into the same issue on the npx impeccable skills install path and put up a fix in #148 that takes the same approach. Two sides of the same problem, might be worth having a look. |
Fixes #46.
This PR adds a convenient shell script (
bin/link.sh) and documentation for using the repository as a git submodule. This allows users to keep their skills up to date withgit submodule update --remotewithout having to manually download ZIPs or run update scripts.The script automatically detects the provider you want and creates a relative symlink from your project's root to the submodule directory.
Usage: