Synchronize Git commits between BladeX repositories with path and package remapping.
npx skills add https://github.com/tiantien/team-ai-coding-plugin --skill blade-sync
Please help me install this Agent Skill. Skill: blade-sync Source: https://github.com/tiantien/team-ai-coding-plugin/tree/main/skills/blade-sync Command: npx skills add https://github.com/tiantien/team-ai-coding-plugin --skill blade-sync
This Skill moves Git commits between BladeX repositories without losing intent, even when the source and target projects use different module layouts or package paths. It helps teams migrate upstream changes, mirror fixes, and keep boot, cloud, and links codebases aligned.
Ask the blade-sync skill to synchronize the selected commit range from the source repository to the target repository, and tell it whether to use mirror mode or adapt mode.
High-intent search queries and answers about installing and using this skill.
To sync Git commits between BladeX Boot and Cloud, use adapt mode to remap file paths, package names, and imports, applying changes commit-by-commit to keep each modification traceable and reviewable.
The safest way to migrate upstream BladeX commits is commit-only synchronization, which blocks dangerous Git actions and enforces manual review checkpoints after each change set to preserve original commit intent.
Yes, you can mirror a fix from one BladeX project to another using mirror mode, which replays source history one commit at a time across Boot, Cloud, and Links codebases while keeping every change reviewable.
Yes, the BladeX commit synchronization process enforces manual review checkpoints by pausing for user confirmation after applying each commit, ensuring commit-only safety constraints block dangerous Git actions during cross-project migration.
Git commits fail when migrating across BladeX projects because heterogeneous module layouts mismatch, requiring adapt mode to automatically adjust file paths and imports during ordered per-commit application.
tiantienCompare BladeX-family repositories and classify architecture-driven differences from business logic gaps.
sasamukuPush code commits to a remote Git repository with branch targeting.
giang6283623Perform threat-model-led security reviews of source code, APIs, and authentication logic.
kriscendobotApply specific git commits across branches to synchronize documentation and configuration files.
