sync
Runs the full project sync pipeline — lifecycle update, audit, L0→L1 publish, commit, push, and PR creation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Runs the full project sync pipeline — lifecycle update, audit, L0→L1 publish, commit, push, and PR creation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Runs the full project sync pipeline — lifecycle update, audit, L0→L1 publish, commit, push, and PR creation.
Turn a topic or your own materials into a single self-contained, interactive HTML report — top tabs, clickable reference drawers, dense tables, comparison heatmaps, inline SVG, in-page search, a light/dark theme toggle, and multilingual support. Use when: user says "/explain-me", "/reportme", "make a report", "create report", "explain this topic". Inspired by beret21/reportme.
Document Production Workflow for co-deck — generates searchable, themed handbooks as static sites (GitHub Pages). Three modes: standalone handbook, lecture companion (reads co-deck slide_deck.md), full course site. Responds to "make handbook", "create handbook", "build course site", "companion handbook" (triggered by Korean phrases too). H-Stage pipeline (H-0 through H-7). Independent from the 11-Stage slide pipeline.
Turn a topic or your own materials into a single self-contained, interactive HTML report — top tabs, clickable reference drawers, dense tables, comparison heatmaps, inline SVG, in-page search, a light/dark theme toggle, and multilingual support. Use when: user says "/explain-me", "/reportme", "make a report", "create report", "explain this topic". Inspired by beret21/reportme.
Pre-edit fact-forcing quality gate. Ensures agents investigate a file's importers, schemas, and scope constraints before making changes. Part of the 3-layer enforcement model (Hook → Prompt → Skill).
Pre-edit fact-forcing quality gate. Ensures agents investigate a file's importers, schemas, and scope constraints before making changes. Part of the 3-layer enforcement model (Hook → Prompt → Skill).
| name | sync |
| description | Runs the full project sync pipeline — lifecycle update, audit, L0→L1 publish, commit, push, and PR creation. |
| version | 1.2.0 |
| last_reviewed | "2026-08-03T00:00:00.000Z" |
| status | active |
| scope | common |
| l2_propagate | true |
| owner | pm |
| prerequisites | Bun runtime |
| metadata | {"type":"process","triggers":["sync","/sync","commit and push","create PR"]} |
Runs the full project sync pipeline (scripts/dev-sync.ts). This is the single mandatory pathway for all workspace commits — it handles lifecycle finalization, audit gating, L0→L1 template propagation, git branch creation, commit, push, and PR creation in one orchestrated flow.
Write the PR body (the agent writes it — never shell out to an LLM CLI):
Inspect the change: git diff HEAD~1 --stat and git diff HEAD~1 --name-only (first 30 files).
Write the body in English using EXACTLY this structure (keep all section headers, fill placeholders):
[1-3 sentences: what problem does this solve and why now?]
[concise bullet list of actual changes — be specific, not generic]
bun scripts/audit.ts passes.env files staged (use .env.sample for templates)[Breaking changes, deployment steps, or reviewer guidance. Write 'None' if not applicable.]
Save it to <git-dir>/sync-pr-body.md, where <git-dir> is git rev-parse --git-dir (e.g. .git/sync-pr-body.md) — outside the working tree so it is never committed.
Run the sync script with the provided arguments, passing the body file:
bun scripts/dev-sync.ts --body-file "$(git rev-parse --git-dir)/sync-pr-body.md" "$ARGUMENTS"
The pipeline executes the following steps in order:
| Step | Name | Fatal? | Description |
|---|---|---|---|
| 0 | CWD Guard | FATAL | Verifies script runs from workspace root; exits if CWD mismatches import.meta.dir/.. |
| 1 | Language Gate | FATAL | Commit message / PR title must be English (CONSTITUTION.md S3); blocks non-English via language-guard.ts |
| 2 | Memory Session Entry | FATAL | Appends session summary (changes, decisions, open issues) to memory/YYYY-MM-DD.md |
| 2 | MEMORY.md Index Sync | FATAL | Updates memory/MEMORY.md index via sync-md.ts |
| 2.5 | scripts/README.md Generation | FATAL | Regenerates scripts/README.md via generate-scripts-readme.ts if the script exists |
| 3 | CHANGELOG.md Check | FATAL | Checks CHANGELOG.md [Unreleased] — blocks and exits if empty (agent must add entries first via /changelog or manual edit) |
| 3.6 | Deprecated Script Warnings | non-fatal | Scans SCRIPTS.md for deprecated scripts and prints warnings |
| 3.7 | L0/L1 Script Drift Check | non-fatal | Runs verify-scripts.ts --check-drift to detect drift between L0 and L1 script copies |
| 3.8 | Memory File Archival | non-fatal | Runs archive-memory.ts to archive old memory files |
| 3.9 | Spec Registry Check | non-fatal | Runs audit.ts --spec-check --lifecycle-only to warn about stale specs |
| 4 | AUDIT GATE | FATAL | Runs audit.ts — must exit 0 before proceeding |
| 4.5 | VERSION_MANIFEST.md Generation | FATAL | Generates VERSION_MANIFEST.md via generate-version-manifest.ts |
| 4.7 | L0 to L1 Publish | FATAL (L0) / non-fatal (L1) | Propagates scripts, skills, commands, docs via propagate-to-templates.ts --apply; fatal only in L0 context (CONSTITUTION.md present) |
| 4.8 | Skill Sync to Platforms | non-fatal | Runs sync-skills.ts to distribute skills to .claude/skills/, .gemini/skills/, .agents/skills/; warnings only |
| 5 | Branch Creation | FATAL | Creates pr/<timestamp>-<slug> branch if on main/master; reuses existing branch otherwise |
| 6 | Sensitive File Guard + Git Add/Commit/Push | FATAL | Guards against .pem, .key, .env, credentials.json, etc.; runs git add -A, git commit, git push |
| 7 | PR Creation | FATAL | If --body-file was passed, validates it (English) and opens the PR via gh pr create --body-file; otherwise falls back to gen-pr-body.ts template, .github/pull_request_template.md, then gh pr create --fill; idempotent — updates existing PR if one already exists for the branch |
All PR titles and bodies generated by this command must be written in English, regardless of the active session language. This applies to the agent-written body in step 1 and to any gh pr create / gh pr edit calls — dev-sync.ts blocks non-English bodies at the same language-guard gate used for commit messages.