Coordinate multi-repo pull requests across JCSDA-internal repositories with merge-order reasoning.
npx skills add https://github.com/travissluka/claude_jedi --skill jedi-prs
Please help me install this Agent Skill. Skill: jedi-prs Source: https://github.com/travissluka/claude_jedi/tree/main/.claude/skills/jedi-prs Command: npx skills add https://github.com/travissluka/claude_jedi --skill jedi-prs
Coordinate multi-repo PRs across JCSDA-internal repos. Handles change analysis, merge-order reasoning, build-group selection, tracking-issue check/creation, body drafting, opening, label lifecycle (bug / waiting for another PR / coordinate merge / ready for merge), and the multi-day follow-up flow (draft→ready, drop stale build-groups). State is persisted in a memory file so a workflow that spans a CI cycle (hours) can be resumed across conversations. Use when: the user is preparing PRs for a feature that touches multiple bundle repos, or wants to resume / inspect / mutate an in-flight coordinated PR set.
Start a new jedi-prs workflow by supplying a <slug> and one or more repo:branch pairs.
High-intent search queries and answers about installing and using this skill.
Coordinating multi-repo pull requests involves aligning changes, merge order, and issue tracking across bundle repositories using a structured draft-to-open-to-close lifecycle. State is persisted in a memory file to track progress.
Yes, resuming a multi-repo PR workflow across conversations is supported by loading a memory-persisted state file. This allows you to pick up in-flight coordinated PR sets, inspect their status, and continue the follow-up flow.
Managing tracking issues and labels for coordinated PRs involves checking or creating a tracking issue, drafting PR bodies, and applying a label lifecycle such as 'waiting for another PR' or 'ready for merge' to synchronize multi-repo changes.
Starting a new PR coordination workflow for multiple GitHub branches requires supplying a slug and one or more repo:branch pairs. The system then performs change analysis, merge-order reasoning, and build-group selection for the set.
Yes, this multi-repo PR coordination tool works specifically with JCSDA-internal repositories. It enforces frontmatter-driven discovery and structured lifecycle management tailored for JCSDA bundle repo feature work.
Dropping stale build-groups during the multi-day PR follow-up flow keeps merge-order reasoning accurate and prevents CI failures. This ensures only valid, current build-groups are tracked in the persisted state.
erikliebenInitialize development sessions by loading user identity, project memory, and workflow configurations.
bybren-llcAutomate PR creation, CI validation, and release coordination in rebase-first workflows.
iamacoffeepotInitialize Aether release workflow labels via GitHub API operations.
hanibalskAutomate GitHub PR creation, review, merge, and CI checks via gh CLI.
