From rafayels-engineering
Pull the latest rafayels-engineering plugin and refresh repo-specific skills with current project context. Run after plugin updates or when CLAUDE.md changes.
npx claudepluginhub rafayelgardishyan/rafayels-engineering[optional: path to the repository, defaults to cwd]re/# Update Plugin & Repo Skills Pull the latest rafayels-engineering plugin from the marketplace and refresh all repo-specific skills with current project details from CLAUDE.md. ## Repository Path <repo_path> #$ARGUMENTS </repo_path> ## Execution Flow ### Phase 1: Determine Repository If no path provided, use the current working directory. Verify `.claude/skills/` exists — if not, suggest running `/re:existing_repo` first. ### Phase 2: Pull Latest Plugin Update the marketplace repo and sync to the cache: Then sync the marketplace source to the cache directory so new skills are ...
/updateUpdates beads issue fields: status, priority, assignee, title, or description. Accepts [issue-id] [value]; prompts interactively if missing. Applies via tool and shows updated issue.
/updateReflects on project changes, investigates impacts, updates stable llmdoc docs in must/, guides/, reference/, syncs index.md, and reports reflection path with changed files.
/updateUpdates statusLine.command path in ~/.claude/settings.json to latest claude-dashboard plugin version from cache. Shows previous/new paths and restart reminder.
/updateChecks metaswarm plugin version against marketplace, applies updates if available (auto for marketplace, migration guide for npm), and verifies skills load correctly.
/updateChecks PDF Playground plugin version, updates to latest via claude plugin update if needed, confirms change, and prompts restart of Claude Code.
/updateUpdates VBW plugin to the latest cached version with automatic cache refresh. Use --check to read current installed version without updating.
Pull the latest rafayels-engineering plugin from the marketplace and refresh all repo-specific skills with current project details from CLAUDE.md.
<repo_path> #$ARGUMENTS </repo_path>
If no path provided, use the current working directory.
REPO="<repo_path or cwd>"
cd "$REPO" && git rev-parse --is-inside-work-tree
Verify .claude/skills/ exists — if not, suggest running /re:existing_repo first.
Update the marketplace repo and sync to the cache:
cd ~/.claude/plugins/marketplaces/rafayels-marketplace && git pull --ff-only
Then sync the marketplace source to the cache directory so new skills are immediately available:
# Remove stale cache and copy fresh
rm -rf ~/.claude/plugins/cache/rafayels-marketplace/rafayels-engineering/1.0.0/skills
cp -r ~/.claude/plugins/marketplaces/rafayels-marketplace/plugins/rafayels-engineering/skills \
~/.claude/plugins/cache/rafayels-marketplace/rafayels-engineering/1.0.0/skills
Also sync commands and agents:
rm -rf ~/.claude/plugins/cache/rafayels-marketplace/rafayels-engineering/1.0.0/commands
cp -r ~/.claude/plugins/marketplaces/rafayels-marketplace/plugins/rafayels-engineering/commands \
~/.claude/plugins/cache/rafayels-marketplace/rafayels-engineering/1.0.0/commands 2>/dev/null || true
rm -rf ~/.claude/plugins/cache/rafayels-marketplace/rafayels-engineering/1.0.0/agents
cp -r ~/.claude/plugins/marketplaces/rafayels-marketplace/plugins/rafayels-engineering/agents \
~/.claude/plugins/cache/rafayels-marketplace/rafayels-engineering/1.0.0/agents 2>/dev/null || true
Parse the repo's CLAUDE.md to extract project details needed for skill customization:
cat "$REPO/CLAUDE.md"
Extract from CLAUDE.md:
# Project: headingLanguage/Framework: lineTest command: lineLint command: lineBuild command: lineDocs location: lineDev logs: lineADRs: lineIf CLAUDE.md doesn't exist or is missing fields, use AskUserQuestion to fill in the gaps.
For each skill in $REPO/.claude/skills/, read the latest template from the plugin cache and re-generate it with the project-specific details:
ls "$REPO/.claude/skills/"
For each installed skill directory:
~/.claude/plugins/cache/rafayels-marketplace/rafayels-engineering/1.0.0/skills/<skill>/SKILL.md$REPO/.claude/skills/<skill>/SKILL.mdKey principle: Upstream additions (new sections, new tools, new instructions) should be added. Project-specific values (paths, project names, commands) should be preserved from the existing repo skill.
Skills to refresh:
For skills that exist upstream but not in the repo, ask:
"New skill <skill_name> is available: <skill_description>. Install it?"
Show what changed by comparing the upstream skill content:
Plugin Update Summary
Plugin version: <version from plugin.json>
Skills updated: <count>
Changes:
- using-adr-plugin: Added merge, split, connections tools + domein field
- <skill>: <description of changes>
New skills available:
- <skill_name>: <description> (installed: yes/no)
Repo skills refreshed:
- check ✓
- test ✓
- fix ✓
- dev-log ✓
- using-adr-plugin ✓
- getting-started ✓
# Check all skills are valid
for skill in "$REPO/.claude/skills"/*/SKILL.md; do
echo "✓ $(dirname $skill | xargs basename)"
done
# Show git diff of changes
cd "$REPO" && git diff --stat .claude/skills/
Ask: "Want to commit these skill updates?" If yes:
git add .claude/skills/
git commit -m "chore: update rafayels-engineering skills to latest upstream"
git pull fails (dirty marketplace repo), run git stash && git pull && git stash pop/re:existing_repo for full setup