.agents/skills/claude-skills-sync-migration/SKILL.md
Scaffold reusable Claude skill-sync automation for migrating repositories. Use when users ask to copy `.agents/skills` into `.claude/skills`, generate `skills:sync:*` scripts, inject package.json scripts/postinstall hooks, or migrate this sync workflow to another project.
npx skillsauth add adonis0123/adonis-skills claude-skills-sync-migrationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
将当前仓库的 skills 同步能力迁移到其他项目时,使用本 Skill。
目标是在目标仓库自动落地以下能力:
scripts/sync-llm-skills.ts,支持 --source、--targets、--dry-run。scripts.skills:sync:llm 命令。devDependencies.is-ci 存在(缺失时自动写入)。postinstall,默认注入 is-ci CI guard。.claude/skills。.gitignore 包含 /.claude/skills。package.json)。.agents/skills(默认值)。.claude/skills(默认且唯一目标)。node /path/to/claude-skills-sync-migration/scripts/bootstrap-sync-skills.mjs --project /path/to/target-repo
--script-name(默认 skills:sync:llm)--script-path(默认 scripts/sync-llm-skills.ts)--skip-postinstall(跳过 postinstall 注入)--script-name 仅允许字符集 [A-Za-z0-9:._-]+,非法值必须失败退出。pnpm run skills:sync:llm -- --dry-run
pnpm run skills:sync:llm -- --targets=claude
scripts/sync-llm-skills.tspackage.json.gitignoreis-ci 依赖处理结果(新增或已存在)。.gitignore 的 /.claude/skills 忽略规则处理结果(新增或已存在)。scripts/bootstrap-sync-skills.mjsassets/templates/sync-llm-skills.tsreferences/integration-checklist.mdpackage.json)。is-ci,必须自动写入 devDependencies.is-ci,再注入 CI guard 命令。tools
Use when the user's pain is "adding/removing one more X means editing N files" and X is a recurring variant kind: popup, banner, modal, ad slot, payment method, AI model/tool, form field type, connector, sub-site, command, menu item, agent, extension point, or data source. Use when they want to design, refactor, review, name, or explain a pluggable mechanism using registry, interface/trait contract, runtime core, and convention folders; mention pluginize, pluggable, plugin architecture, extension point, registry pattern, or extensibility. Use when explaining the first-principles rationale, DDD/SOLID/OCP mapping, or industry analogies behind that structure. Use for cross-stack mapping to VSCode contributes, Webpack/Vite plugins, Rust/Tauri connectors, Python entry_points, or cargo features. Skip one variant's internals/styles/hooks/copy/bugs, and skip register/registry meaning DI container, user signup, or package registry.
development
Use BEFORE heavier workflow skills when route choice matters. Route creative work without a design doc/spec to Brainstorm; destructive or hard-to-reverse work to Discuss; unresolved decisions, Plan/Full fan-out, ship checks, unclear bugs, and fresh-eyes fix-then-re-review need this gate. Skip single-line read-only lookups, pure typo/formatting edits, trivial safe one-line fixes, and clearly safe named-skill requests. Outputs Route, Runtime skill, Fallback alias, and Execution path.
development
Cross-agent code review handoff and review-fix-re-review loop with persistent packet artifacts. Requires a git repo because packet addressing uses git rev-parse --show-toplevel. Use when the user asks for an independent, read-only second pair of eyes on a diff/branch/PR another agent or teammate implemented; asks to verify reviewer feedback before fixing; says a fix is done and wants scoped re-review; asks to continue the latest review packet; or asks for first-principles, DDD, high-cohesion/low-coupling review. Persists each loop under $repo_root/.review-handoff/active/ so agents can resume without copy-paste. Do NOT use for ordinary implementation, generic staged-change review, review-comment copy editing, non-git folders/zips/tarballs/temp dirs, or when the user names a different review skill.
testing
Enforces 'decide then plan' discipline - the pre-planning decision gate. Use when the user asks for a plan or starts a change while key decisions are unresolved: architecture tradeoffs, data flow, public interfaces, unclear requirements, multi-module scope, or roughly 5+ files affected. Also triggers when the user explicitly wants to discuss, compare options, or review architecture before committing. Core job: reduce incorrect-execution cost by confirming decisions before producing executable plans.