| name | hydrate-propose |
| description | Stage reconciled drafts as a single commit (or PR for multi-developer projects) that updates the working memory files in a reviewable batch. activeContext.md is excluded. After acceptance, the synchronizer agent takes over for ongoing maintenance.
|
hydrate-propose
Input: annotated drafts from hydrate-reconcile.
When this skill is activated:
- Group drafts by target file. One commit (or PR) updates multiple working memory files in a coherent batch.
- Write the proposed changes to each file:
- Append-only updates to
decisionLog.md (most recent at top)
- Section updates in
projectOverview.md, conventions.md, dataContracts.md
- New entries in
openQuestions.md
- Skip
activeContext.md entirely
- Write the proposed commit message: a one-line summary plus a body that lists each draft and its source provenance.
- For solo or small-team repos: stage the commit and leave it for the developer to review and commit.
- For multi-developer repos: open a PR. Tag reviewers based on CODEOWNERS or recent committers to the relevant files.
Output
A staged commit (or open PR), with all drafts applied and a clear commit message.
What this skill does NOT do
- It does not auto-commit. Solo flow: changes are staged for review. Team flow: PR awaits review.
- It does not touch
activeContext.md. That file is per-developer and gitignored.
- It does not run the synchronizer agent. Synchronization is ongoing maintenance; hydration is the deeper periodic job. Different cadences.
Common gotchas
- Rewriting
decisionLog.md instead of appending. The decision log is append-only; never edit past entries.
- Forgetting source provenance in the commit body. Reviewers use provenance to trust the drafts.
- Including
activeContext.md in the proposed commit. It's gitignored and per-developer; never propose changes to it.
