Project Context Sync

**Judgement:** A well-scoped, practical skill for maintaining a living project status document tied to git commits. It’s especially useful in AI-assisted workflows and for developers who frequently switch contexts or share projects. **What it’s good at:** - Automatically generates and updates `PROJECT_STATE.md` on every commit using a post-commit hook. - Captures last commit details, recent history, branch, changed files, and optional diff stats. - Optionally calls an LLM (via Clawdbot’s HTTP gateway) to infer current focus and suggest next steps. - Offers a non-AI mode that uses only raw git info, which is fast and cost-free. - Easy installation/uninstallation scripts and a straightforward YAML config file. **Key risks / limitations:** - **Gateway/LLM exposure:** AI mode sends commit/context data through Clawdbot’s OpenAI-compatible endpoint. While it’s loopback-bound and token-protected by default, misconfiguration or credential leakage could expose sensitive repo information. - **Hook fragility:** The post-commit hook can be overwritten by other tools or manual changes, breaking automatic updates unless reinstalled. - **Latency & cost in AI mode:** Each commit may incur LLM latency and token costs, which can add up in very high-commit workflows. - **AI reliability:** Summaries and “suggested next steps” may occasionally be inaccurate or overconfident; they should be treated as guidance, not ground truth. **Recommended scenarios:** - Individual developers or small teams using Clawdbot who want a continuously updated, human-readable project status file. - Repos where AI agents or tools frequently need a quick snapshot of recent work and current focus. - Projects with frequent handoffs or intermittent work, where remembering context and next steps is a recurring pain point. **Less ideal for:** - Highly sensitive codebases where sending any project context to an LLM (even via a local gateway) is disallowed. - Workflows that already use heavily customized git hooks that might conflict with additional post-commit scripts. - Extremely high-frequency commit patterns where additional post-commit processing time is unacceptable.