Sync JEDI bundle repos and analyze changes against origin/develop.
npx skills add https://github.com/travissluka/claude_jedi --skill update-repos
Please help me install this Agent Skill. Skill: update-repos Source: https://github.com/travissluka/claude_jedi/tree/main/.claude/skills/update-repos Command: npx skills add https://github.com/travissluka/claude_jedi --skill update-repos
This Skill keeps the JEDI bundle in sync by fetching and merging develop across repos, surfaces what changed since the Claude docs were last updated, and proposes targeted documentation updates with user review, plus a cross-repo impact summary for active projects.
Run the update-repos skill to sync all repos, analyze changes since origin/develop, and prepare doc updates for review.
High-intent search queries and answers about installing and using this skill.
To sync multiple git repositories, this skill fetches and merges origin/develop across the JEDI bundle using bash scripts. It analyzes what changed since the last documentation update and generates a cross-repo impact summary for review.
Updating documentation after syncing bundle repositories involves a three-phase process: git sync, change analysis against origin/develop, and proposed targeted doc edits. The skill outputs a Phase 4 summary for user review before changes are finalized.
Yes, you can track undocumented and external repos in a bundle sync. The skill applies to documented, undocumented, and external repositories in the JEDI bundle, guiding git sync and change analysis across all included repos.
You do not need external dependencies to run batched git operations. The skill uses bash-based scripts located in the skill's scripts directory to perform batched operations against origin/develop without requiring additional packages.
Cross-repo impact analysis works by comparing recent git history against the point where Claude docs were last updated. It surfaces relevant changes across the bundle and generates a summary report detailing how active projects are affected.
A key limitation of automating documentation updates is that it only proposes targeted doc edits for review. The skill does not automatically publish changes; it outputs a summary so users can manually verify cross-repo impacts before applying edits.
smallorbitCreate and checkout Git branches from origin/develop.
otrebuList and delete merged Git branches with user confirmation.
ez404-36Analyze git history to generate changelogs, track documentation freshness, and validate cross-references.
dnvitiMerge develop into main and push both branches to origin.
