project-wiki-sync

name	project-wiki-sync
description	Manage shared team context for vibe-coding projects from a GitHub repository link. Use when the user mentions project-wiki-sync, vibe coding, LLM wiki, Claude Code/Codex context drift, daily updates, handoff notes, shared project docs, or asks to install/use a skill that keeps team coding work aligned around one GitHub project.

Project Wiki Sync

Overview

Use this skill to keep a team of Claude Code/Codex users aligned while each person vibe-codes in separate LLM sessions. The skill creates and maintains a small GitHub-backed project wiki, start prompts, daily updates, decisions, and handoff notes.

First Response Rule

If the user's message does not include the target coding repository URL, ask exactly:

바이브코딩할 GitHub 링크가 뭐예요?

Do not ask for the skill repository URL. This skill repository is only the installer/source. The target URL is the repository where the team will code.

If the target repository URL is present but the task is missing, initialize the wiki first, then ask:

오늘 바이브코딩할 작업은 뭐예요?

Workflow

1. Resolve this skill's directory and use scripts/wiki_sync.py from that directory.
2. Read references/context-contract.md before initializing or changing wiki files.
3. If the target repository is not cloned locally, clone it. If the current directory is already that repository, use it in place.
4. Run initialization:

python <skill-dir>/scripts/wiki_sync.py init --repo-url <target-github-url>

5. Start a coding session by creating a context prompt:

python <skill-dir>/scripts/wiki_sync.py start --task "<today's task>" --project-dir <local-project-path>

Paste or load the generated prompts/current_vibe_prompt.md into the active LLM session before making code changes.

6. End a session by recording the handoff:

python <skill-dir>/scripts/wiki_sync.py end --name "<person-name>" --project-dir <local-project-path>

Use --commit to commit the generated wiki updates. Use --push only when the user wants the update pushed to GitHub.

Context Contract

Keep these files as the shared source of truth in the target project:

• docs/wiki/00_project_context.md
• docs/wiki/01_current_scope.md
• docs/wiki/02_data_sources.md
• docs/wiki/03_architecture.md
• docs/wiki/04_decisions.md
• docs/wiki/05_handoff.md
• docs/wiki/daily/YYYY-MM-DD.md
• prompts/current_vibe_prompt.md

Treat 04_decisions.md as stronger than chat memory. When code, UX, data scope, or model scope changes, update the decision log.

Operating Rules

• Prefer the target repository's existing files over assumptions.
• Never claim raw data exists unless the repository or source docs prove it.
• Separate product scope, data availability, model features, and UX assumptions.
• Keep daily updates short enough for Teams or GitHub comments.
• If multiple team members are working, preserve their notes and append new updates instead of rewriting history.
• If generated docs already exist, update them in place rather than replacing them.

Useful Commands

python <skill-dir>/scripts/wiki_sync.py doctor --project-dir <local-project-path>
python <skill-dir>/scripts/wiki_sync.py start --task "데이터 전처리" --project-dir <local-project-path>
python <skill-dir>/scripts/wiki_sync.py end --name "준형" --summary "전처리 기준 정리" --commit