ワンクリックでManusで任意のスキルを実行

hydrate-reconcile

スター2

フォーク0

更新日2026年6月7日 20:48

Compare drafts against existing working memory and against the codebase. Annotates each draft as net-new, would-overwrite, or conflicts-with-code. Greenfield projects skip the existing-working-memory comparison.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

kendrick

kendrick/dotfiles

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

hydrate-reconcile

Input: drafts from hydrate-draft.

When this skill is activated:

For each draft, check against existing working memory if present:
- Net new: no matching content; safe to add.
- Would overwrite: existing content covers the same territory; surface the diff.
For each draft, sanity-check against the codebase. The draft asserts something; does the code agree?
- If yes: leave the annotation as-is.
- If no: flag as conflicts with code. Either the draft is wrong (extracted from stale source) or the code is wrong (drift from stated intent). Investigation needed.
Output the drafts plus annotations.

Output

The original drafts plus a reconciliation block per draft.

Common gotchas

Trusting a stale README over current code. The README is a source, but it can lie. When in conflict, the code is more often right.
Flagging convention drafts as "conflicts" when the code has multiple patterns. The convention is the dominant pattern; minority patterns are noise unless they're the new direction.
Treating an existing working memory entry as authoritative when it predates a major refactor. git log _working-memory/<file>.md tells you when the entry was last touched. If the codebase moved on, the entry needs updating.

このリポジトリの他の Skills

同じリポジトリ

hydrate-discover

kendrick/dotfiles

Inventory the source surface for hydrating working memory in this repo. Surveys manifests, code structure, README, ADRs (if any), recent git history, and code patterns. Run once when populating working memory beyond the scaffold prompt's pre-population.

2026-06-072

hydrate-draft

kendrick/dotfiles

Map findings into the six working memory files: projectOverview, decisionLog, dataContracts, conventions, openQuestions. Drafts include source provenance inline. activeContext.md is excluded; the developer drives that file directly.

2026-06-072

hydrate-extract

kendrick/dotfiles

Pull findings from a single source location. Each finding is one sentence about a fact, decision, convention, or contract, plus a pointer back to source. Deterministic for structured sources, AI semantic for prose.

2026-06-072

hydrate-propose

kendrick/dotfiles

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.

2026-06-072

update-working-memory

kendrick/dotfiles

Reads the current working memory state, diffs it against recent git changes, and proposes updates. Use when finishing a feature, resolving a decision, or when active context feels stale.

2026-06-072

name	hydrate-reconcile
description	Compare drafts against existing working memory and against the codebase. Annotates each draft as net-new, would-overwrite, or conflicts-with-code. Greenfield projects skip the existing-working-memory comparison.

hydrate-reconcile

Input: drafts from hydrate-draft.

When this skill is activated:

For each draft, check against existing working memory if present:
- Net new: no matching content; safe to add.
- Would overwrite: existing content covers the same territory; surface the diff.
For each draft, sanity-check against the codebase. The draft asserts something; does the code agree?
- If yes: leave the annotation as-is.
- If no: flag as conflicts with code. Either the draft is wrong (extracted from stale source) or the code is wrong (drift from stated intent). Investigation needed.
Output the drafts plus annotations.

Output

The original drafts plus a reconciliation block per draft.

Common gotchas

Trusting a stale README over current code. The README is a source, but it can lie. When in conflict, the code is more often right.
Flagging convention drafts as "conflicts" when the code has multiple patterns. The convention is the dominant pattern; minority patterns are noise unless they're the new direction.
Treating an existing working memory entry as authoritative when it predates a major refactor. git log _working-memory/<file>.md tells you when the entry was last touched. If the codebase moved on, the entry needs updating.