메뉴
Cross-repo consistency routine dispatched by the heartbeat. Checks spec drift and synchronizes community files across all SDK repositories. Use when the heartbeat needs to verify spec alignment and community file consistency.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | routine-sync |
| description | Cross-repo consistency routine dispatched by the heartbeat. Checks spec drift and synchronizes community files across all SDK repositories. Use when the heartbeat needs to verify spec alignment and community file consistency. |
Dispatched by the heartbeat. Checks spec drift and cross-repo consistency, then dispatches to sdk-bootstrap (spec updates) and sdk-sync (community files).
Rules: change-control · contribution · safety
quick (regular heartbeat) or full (full heartbeat). The heartbeat dispatcher provides this — use quick for step 2 of The Loop, full for step 1 of Periodic Checks.Run bash scripts/spec-status.sh with the appropriate flag for the current mode:
bash scripts/spec-status.sh --quick (1 API call)bash scripts/spec-status.sh (no --quick, catches manual submodule updates)Then:
sdk-bootstrap for each outdated SDK to update the submodule to the latest spec tag.NOT_FOUND repos: Run sdk-bootstrap Phase 0 if Albert has org permissions, otherwise wait for a human. Log the blocker in memory/YYYY-MM-DD.md.Run sdk-sync Phase 1 (Audit) to detect community file drift across all SDK repositories.
If drift is detected in Step 2:
sdk-sync Phase 2 (Generate patches) to create the necessary changes.sdk-sync Phase 3 (Open PRs) to open PRs for all repos with drift.scripts/spec-status.shsdk-bootstrap (if any)sdk-sync Phase 1memory/YYYY-MM-DD.mdGenerate a weekly status summary covering PRs opened/merged/closed by Albert, issues triaged, spec alignment progress, and blockers awaiting human input.
Triage incoming GitHub issues across supervised Altertable repositories. Use when processing new issues, labeling bugs and feature requests, detecting duplicates, requesting minimal reproductions, or marking stale issues.
Notification-driven maintainer routine to identify actionable work across supervised Altertable repositories. Relies on GitHub notifications and API to monitor activity and respond to issues and PRs requiring attention. Use when starting a maintenance session to process notifications and prioritize work.
Bootstrap or update an Altertable SDK repository from a versioned API spec. Use when given a target GitHub repository (e.g. altertable-ai/altertable-lakehouse-ruby) and a spec version tag (e.g. v0.1.0) to set up a git submodule, implement missing functionality, and submit a PR. Also use when a new spec version is released and the SDK needs to be updated to match.
Defines conventions for releasing open-source SDKs and libraries. Use when releasing a new version of an SDK, writing changelogs, or publishing to a language registry (npm, PyPI, Maven, etc.).
Keep shared configuration, community files, and CI templates consistent across all SDK repositories. Use when auditing cross-repo consistency or propagating a change (license, contributing guidelines, CI updates, bot config) to multiple SDK repos.