菜单
Sync Faru backlog cards with GitHub issues in both directions — create the missing GH issue for every todo/wip card and the missing card for every open issue. Use for 'sync issues', 'cards to issues', 'GH issue coverage', 'reconcile backlog'. Not for closing/triaging issues.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Expert guidance for the App Intents framework on Apple platforms. Use when developers mention: (1) Siri or Shortcuts integration, (2) AppIntent, AppEntity, AppEnum, or AppShortcutsProvider, (3) Spotlight actions or indexed entities, (4) exposing app features to Apple Intelligence, (5) parameters, parameter summaries, or intent donation, (6) widget/control configuration intents. Not for widget timeline design itself (see widgetkit-live-activities skill).
Expert guidance for CloudKit sync on Apple platforms. Use when developers mention: (1) iCloud sync or cross-device sync of app data, (2) SwiftData + CloudKit or NSPersistentCloudKitContainer, (3) CKSyncEngine or custom CloudKit record sync, (4) CloudKit sharing / collaboration (CKShare), (5) CloudKit entitlements, containers, or schema deployment, (6) conflict resolution or offline-first with iCloud. Not for third-party sync backends (Firebase, Supabase) and not for app-server REST sync (see docs/api/sync.md).
Expert guidance for StoreKit 2 in-app purchases and subscriptions on Apple platforms. Use when developers mention: (1) in-app purchases, IAP, or subscriptions, (2) Product, Transaction, or currentEntitlements, (3) receipt validation or transaction verification, (4) SubscriptionStoreView / StoreView / ProductView, (5) restore purchases, offer codes, promotional offers, refunds, (6) StoreKit Testing in Xcode or sandbox testing. Not for RevenueCat or third-party billing SDKs.
Apple Human Interface Guidelines for visionOS (Apple Vision Pro). Use when designing or building spatial apps: (1) windows, volumes, and immersive spaces, (2) ornaments, glass material, and spatial layout, (3) eye/hand input, hover effects, and target sizes, (4) comfort, motion, and immersion levels, (5) porting an iOS/iPadOS app to visionOS, (6) RealityKit + SwiftUI scene composition. Companion to the ehmo *-design-guidelines skills for the other Apple platforms.
Expert guidance for WidgetKit widgets and ActivityKit Live Activities on Apple platforms. Use when developers mention: (1) home screen / lock screen / StandBy widgets, (2) Live Activities or Dynamic Island, (3) widget timelines, TimelineProvider, or reload budgets, (4) interactive widgets with App Intents buttons/toggles, (5) Control Center controls (ControlWidget), (6) updating a Live Activity via APNs push. Not for Siri/Shortcuts intents themselves (see app-intents skill).
Audit the health of your Claude Code configuration across all six layers — permissions, hooks, MCP servers, installed skills, agents, settings conflicts. Use when asked to "/health", "check my Claude Code config", "audit my setup", or before debugging unexpected behavior (silent permission denials, MCP tool not appearing, hooks not firing).
| name | sync-issues |
| description | Sync Faru backlog cards with GitHub issues in both directions — create the missing GH issue for every todo/wip card and the missing card for every open issue. Use for 'sync issues', 'cards to issues', 'GH issue coverage', 'reconcile backlog'. Not for closing/triaging issues. |
| context | fork |
Réconciliation bidirectionnelle entre les cartes Faru (docs/backlog/*/CARD.md)
et les issues GitHub du repo. Garantit l'invariant :
Toute carte
todo/wip↔ une issue GH ouverte, et toute issue GH ouverte pertinente ↔ une carte.
Le travail mécanique vit dans framework/tools/sync-issues.sh (0 token, réutilisable
par un hook ou une routine cron). Cette skill est l'enveloppe d'invocation.
Prérequis : gh authentifié (gh auth status), projet en mode Faru (docs/backlog/ présent).
Matérialisé des deux côtés → idempotent (deux exécutions = no-op) :
| Côté | Marqueur |
|---|---|
| Carte | issue: <N> dans le frontmatter |
| Issue | <!-- ulk:card:<slug> --> dans le corps + ligne Carte : \docs/backlog/…`` |
/sync-issues — prévisualiser (dry-run)framework/tools/sync-issues.sh
Affiche le plan sans rien muter : cartes todo/wip sans issue, issues ouvertes sans carte,
et le bilan chiffré. Aucune issue ni carte n'est créée.
/sync-issues apply — appliquerframework/tools/sync-issues.sh --apply
bug/enhancement selon
le type: de la carte), écrit issue: N dans le frontmatter, pose le marqueur dans l'issue.docs/backlog/YYYY-MM-DD-<type>-<slug>/CARD.md
(type déduit des labels : bug→fix, enhancement→feat, sinon task), y écrit issue: N,
et pose le marqueur <!-- ulk:card:<slug> --> dans le corps de l'issue.⚠️ Action sortante : --apply crée des issues publiques et édite leur corps.
Toujours lancer un dry-run d'abord et confirmer le volume.
| Flag | Effet |
|---|---|
--apply | Applique (défaut : dry-run) |
--no-up | Désactive le sens carte → issue |
--no-down | Désactive le sens issue → carte |
--statuses "todo wip" | Statuts de cartes considérés actifs (défaut : todo wip doing in-progress) |
--exclude-labels "a b" | Labels d'issues à ne pas transformer en carte (défaut : dependencies wontfix duplicate invalid question) |
dependabot / renovate / github-actions / *[bot]* ignorés
(ex. #7 Dependency Dashboard).dependencies, wontfix, duplicate, invalid, question.issue: ou marqueur dans le corps)
n'est jamais redupliquée.Le script étant sans état et idempotent, il se câble tel quel :
/schedule ou agent routine (53) : sync-issues.sh --apply 1×/jour.🔗 sync-issues · repo=izo/Ulk · mode=DRY-RUN (aucune mutation)
── MONTANT · cartes todo/wip sans issue ──
➕ créerait une issue ← 2026-06-28-SPEC-HERMES-TASK-RUNNER (type=spec, label=—)
── DESCENDANT · issues ouvertes sans carte ──
➕ créerait 2026-07-04-fix-sentinel-sh-…/CARD.md ← #230 (sentinel.sh: …)
⤫ #7 ignorée (label exclu : dependencies)
── Bilan (DRY-RUN) ──
issues créées (montant) : 34
cartes créées (descend.): 5