From kde-plasmoid-dev
Use when the user wants to mirror or sync a GitHub-hosted plasmoid (or any repo) to an OpenCode mirror repo for wider distribution. Triggers on phrases like "sync to opencode", "mirror to opencode", "push this to opencode", "update the opencode copy", "distribute this widget on opencode". Handles first-time clone of the OpenCode counterpart, rsync of source files (excluding `.git` and the sync helper itself), and a commit + push on the OpenCode side.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin kde-plasmoid-devThis skill uses the workspace's default tool permissions.
OpenCode is a separate git host (e.g. `git@opencode.net:<user>/<repo>.git`) the user maintains as a distribution channel parallel to GitHub. This skill keeps the OpenCode copy in sync with the canonical GitHub working tree.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
Guides code writing, review, and refactoring with Karpathy-inspired rules to avoid overcomplication, ensure simplicity, surgical changes, and verifiable success criteria.
Share bugs, ideas, or general feedback.
OpenCode is a separate git host (e.g. git@opencode.net:<user>/<repo>.git) the user maintains as a distribution channel parallel to GitHub. This skill keeps the OpenCode copy in sync with the canonical GitHub working tree.
~/repos/github/my-repos/<Repo-Name>/ (Train-Case)~/repos/other-networks/opencode/<repo-name>/ (kebab-case, lower-case).git/ and its own origin pointing at the OpenCode host.If those paths don't exist on the user's machine, ask before creating them.
~/repos/other-networks/opencode/<repo-name>/:
git clone git@opencode.net:<user>/<repo-name>.git ~/repos/other-networks/opencode/<repo-name>
SOURCE=~/repos/github/my-repos/<Repo-Name>
DEST=~/repos/other-networks/opencode/<repo-name>
rsync -av --delete \
--exclude='.git' \
--exclude='sync-to-opencode.sh' \
--exclude='.github' \
"$SOURCE/" "$DEST/"
Key flags:
--delete keeps the mirror a true reflection of the source — files removed in the canonical repo are removed in the mirror.--exclude='.git' is mandatory — the mirror has its own git history.--exclude='sync-to-opencode.sh' keeps the mirror clean of the maintenance script (which is GitHub-side only).--exclude='.github' skips GitHub-specific workflows that won't run on OpenCode.Then commit and push from the mirror:
cd "$DEST"
git add -A
if ! git diff --cached --quiet; then
git commit -m "Sync from upstream $(date -u +%Y-%m-%d)"
git push
else
echo "No changes to mirror."
fi
If the canonical repo doesn't already have a sync-to-opencode.sh, offer to drop one in so the user can run the sync without invoking the skill. Template:
#!/bin/bash
SOURCE_DIR="<absolute path to canonical repo>"
DEST_DIR="<absolute path to opencode mirror>"
rsync -av --delete \
--exclude='.git' \
--exclude='sync-to-opencode.sh' \
--exclude='.github' \
"$SOURCE_DIR/" "$DEST_DIR/" || { echo "rsync failed"; exit 1; }
cd "$DEST_DIR" && git add -A
if ! git diff --cached --quiet; then
git commit -m "Sync from upstream $(date -u +%Y-%m-%d)"
git push
else
echo "No changes to mirror."
fi
chmod +x sync-to-opencode.sh after writing.
--delete rsync into a path that isn't a known OpenCode mirror — confirm the destination has an OpenCode origin first:
git -C "$DEST" remote get-url origin | grep -q opencode || { echo "Not an OpenCode mirror — refusing"; exit 1; }
git push on a dirty tree silently leaves uncommitted changes behind.git -C "$SOURCE" status --porcelain first; if non-empty, ask the user whether to proceed.When asked to sync:
origin.git -C "$DEST" status + git -C "$DEST" diff --stat HEAD) before committing.