From plugin-dev-sync
Use when the user asks to "sync plugin-dev", "update plugin-dev from latest docs", "run plugin-dev-sync", or invokes /plugin-dev-sync:sync. Orchestrates the full autonomous pipeline: fetch resources, discover features, diff against plugin-dev, review, apply patches, commit, and create a PR with a full report.
npx claudepluginhub karimstekelenburg/k3m-marketplace --plugin plugin-dev-syncThis skill is limited to using the following tools:
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.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides slash command development for Claude Code: structure, YAML frontmatter, dynamic arguments, bash execution, user interactions, organization, and best practices.
Orchestrate a full autonomous sync of plugin-dev against the latest Claude Code documentation and community resources. Every change is committed and submitted as a PR with a detailed report.
fetch → discover → diff → review → worktree → apply → changelog → push → PR
Run the fetch script to update the local cache:
uv run ${CLAUDE_PLUGIN_ROOT}/scripts/fetch-resources.py
Read data/fetch-report.json to verify fetch success. If critical resources
failed (official-docs, github releases), abort and report the failures.
Launch the discovery-crawler agent to analyze cached content:
data/cache/ and data/resources.jsonThe agent should cross-reference multiple sources. A feature mentioned in release notes AND docs is high-confidence. A feature only on Twitter is low-confidence and should be flagged.
Compare the discovered feature map against the current state of plugin-dev:
Launch the diff-reviewer agent with the diff report:
Drop any changes the reviewer rejects. Log rejections in the PR report.
Parse $ARGUMENTS for --dry-run and --category flags.
If there are approved changes (and not --dry-run):
All sync work happens in an isolated worktree:
BRANCH="plugin-dev-sync/sync-YYYY-MM-DD-HHMMSS"
WORKTREE="/tmp/k3m-sync-$$"
git worktree add -b "$BRANCH" "$WORKTREE" main
cd "$WORKTREE"
After all plugin-dev changes are committed, update plugins/plugin-dev/CHANGELOG.md:
# Changelog
All notable changes to plugin-dev are documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/).
Example:
## 2026-03-28
- **Fixed**: Hook timeout defaults corrected from 60s to 600s
- **Removed**: Fabricated WebSocket MCP transport
- **Added**: 16 missing hook events documentation
- **Added**: `http` and `agent` hook handler types
docs(plugin-dev): update changelog for sync YYYY-MM-DDgit push -u origin "$BRANCH"
gh pr create --title "fix(plugin-dev): sync against latest docs YYYY-MM-DD" --body "$(cat <<'EOF'
<PR body — see format below>
EOF
)"
cd -
git worktree remove "$WORKTREE"
Report the PR URL to the user.
## Plugin-Dev Sync Report
**Date**: YYYY-MM-DD
**Resources fetched**: X/Y successful
**Changes proposed**: N
**Changes approved**: M (K rejected by reviewer)
## Changes Applied
### [Change Title]
- **Type**: outdated | missing | deprecated
- **Confidence**: high | medium | low
- **Files modified**: list of files
- **Sources**: [Source Name](url), [Source Name](url)
- **Reasoning**: Why this change was made
### ...
## Rejected Changes
### [Change Title]
- **Reason for rejection**: reviewer's reasoning
- **Sources checked**: ...
## Validation Results
- `claude plugin validate`: PASS/FAIL
- Skill trigger test: PASS/FAIL
- Agent YAML parse: PASS/FAIL
If --dry-run is passed, stop after Step 4 and print the approved diff
report without applying changes or creating a PR.
The default target is the sibling plugin-dev directory:
${CLAUDE_PLUGIN_ROOT}/../plugin-dev
claude plugin validate fails after patching, revert the last change and retry