docs: TRAC-1236 unify integration-branch sync into one /sync-integration-branch skill#3127
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Bundle Size ReportComparing against baseline from No bundle size changes detected. |
Unlighthouse Performance Comparison — VercelComparing PR preview deployment Unlighthouse scores vs production Unlighthouse scores. Summary ScoreAggregate score across all categories as reported by Unlighthouse.
Category Scores
Core Web Vitals
|
64184c1 to
193b51c
Compare
193b51c to
afe9cb4
Compare
Replace the branch-specific /sync-makeswift skill (and the proposed /sync-b2b-makeswift skill) with a single parameterized /sync-integration-branch skill. The target integration branch is passed as an argument; SKILL.md holds the generic sync flow, and each supported branch has a reference file (references/<name>.md) with its upstream, package identity, integration surface, and branch-specific caveats. Phase 0 resolves the target and loads the matching reference. When no branch is given, or the branch is unknown or absent on origin, the skill lists the valid integrations/* targets and asks the user to pick one. Point the release-catalyst skill at the new skill name. Refs TRAC-1236 Co-Authored-By: Claude <noreply@anthropic.com>
afe9cb4 to
6482e12
Compare
Jira: TRAC-1236
What/Why?
Replaces the branch-specific
/sync-makeswiftskill (and the earlier proposed/sync-b2b-makeswiftskill this PR originally added) with a single parameterized/sync-integration-branchskill.The two per-branch skills were ~90% identical — same four-phase flow (merge → PR → rebase → cleanup), differing only in which branches, package name, and integration files were involved. That duplication meant every fix (e.g. the recent
catalyst.refclobbering guard) had to be applied twice and could drift.Structure (progressive disclosure):
SKILL.mdholds the generic flow and the conflict rules common to every integration branch (package name/version, nestedcatalyst.ref,.changeset/config.jsonbaseBranch,prevent-invalid-changesetstargeting, sharedchangesets-release.yml, lockfile handling, one-time catch-up).references/—references/makeswift.md,references/b2b-makeswift.md— holding only that branch's specifics: upstream (merge source), package identity, sync-branch name, merge-base pair, integration surface, and branch-only caveats.integrations/*branch = a new reference file plus one table row.Argument handling:
integrations/b2b-makeswift) or a shorthand (b2b-makeswift,makeswift).git ls-remote --heads origin) → the skill lists the validintegrations/*targets and asks the user to pick one.release-catalystskill updated to invoke/sync-integration-branch integrations/makeswift.Rollout/Rollback
Local tooling only (
.claude/skills/), no runtime/app impact. Rollback = revert the commit.Note: the literal
/sync-makeswiftslash command is removed; natural-language "sync makeswift" still routes here via the skill description.Testing
Skill markdown only. Verified the net diff vs
canaryis: deletesync-makeswift/SKILL.md, addsync-integration-branch/SKILL.md+ tworeferences/*.md, one-linerelease-catalystreference update. No code paths exercised.