القائمة
Carry richer onboarding memory from a source branch into official memory only when the corresponding code has landed on the official branch.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
After the MCP installs the runtime and skills (scaffolding), take over the rest of setup: install a start-of-session/chat hook (or place the coordinator directive in the harness's always-on instructions), set up the memory repo (ask scaffold vs existing), bootstrap onboarding when scaffolding new, and configure providers to index the code and memory.
Initialize or repair the Agents Remember memory root for a target repository. Defaults to repo-local internal memory; creates an external memory repo only when the developer explicitly asks for external memory.
Capture confirmed findings, route them to the right durable task-local path, and propagate factual current-state clarifications into onboarding immediately when allowed.
Bootstrap onboarding for undocumented repos or existing memory slices. Builds root overviews, route-local overview pillars, evidence packs, file cards, onboarding waves, deleted-slice cleanup, curator reviews, and handoff while keeping the orchestrator thin.
Choose retrieval strategies across memory substrates: semantics for known concepts with unknown structure, relationships for known anchors with unknown connections, and intent for hidden contracts and code truths.
Create and maintain file-level onboarding and repo entity catalogs. Enforces strict 1-to-1 source mapping, governing overview links, metadata, and references, and routes package/module/source-slice create, refresh, move, or delete cases to the c-03-repo-bootstrap skill.
| name | c-11-memory-carryover-from-branch |
| description | Carry richer onboarding memory from a source branch into official memory only when the corresponding code has landed on the official branch. |
Use this skill when a protected official code branch receives delayed or batched merges, while a developer has accumulated richer onboarding on another branch. The source branch may be a personal workbench branch, an individual feature branch, or a handpicked branch processed as part of a larger reconciliation pass.
The c-11-memory-carryover-from-branch skill is not a Git merge. It is a selective memory reconciliation step. It proves which source-branch code changes are represented in the official branch, then carries only the corresponding onboarding into official memory and refreshes verification metadata against the official code commit.
Use the Agents Remember MCP memory carryover tools as the normal installed runtime entry point:
memory_carryover_plan(repo_id="<repo-id>", source_memory="<source-memory-repo>", official_code_ref="<official-ref>", source_code_ref="<source-ref>", old_base="<base-ref-or-sha>")
memory_carryover_apply(repo_id="<repo-id>", source_memory="<source-memory-repo>", official_code_ref="<official-ref>", source_code_ref="<source-ref>", old_base="<base-ref-or-sha>", intent_note="<developer intent>")
Run memory_carryover_plan first. Use memory_carryover_apply only after
reviewing the candidate report. Apply mutates official memory only; it does not
move code branches. The skill tree is instruction-only; installed and
development workflows use the MCP/package route.
exact-landed-commit: at least one commit that touched the source path on the source branch is an ancestor of the official code ref.patch-id-match: the old-base-to-source-branch patch for the source path matches the old-base-to-official patch.final-content-match: the source file content at the source branch ref matches the content at the official ref.same-path-changed: both branches changed the same source path, but the c-11-memory-carryover-from-branch skill did not prove equivalent code.not-landed: the source path changed on the source branch but not on the official branch.Only proven tiers are auto-carry candidates. Same-path overlap is review-required by default because another developer may have changed the same file independently.
would-carryover: dry-run plan with candidate decisions.carried-over: official memory content and ledger commits were created.nothing-to-carryover: no selected candidate changed official memory.blocked: apply was requested without approval, dirty official memory, missing ledger, or missing required candidate data.c-11-memory-carryover-from-branch skill must not copy source branch memory for code that did not land.c-11-memory-carryover-from-branch skill must not copy source branch ledger rows into official memory.c-11-memory-carryover-from-branch skill must refresh carried onboarding metadata to the official code commit, not the source branch commit.c-11-memory-carryover-from-branch skill must not auto-carry same-path-only evidence.c-11-memory-carryover-from-branch skill must not overwrite existing different official onboarding unless replace_existing=true or explicit review-required inclusion is used.c-02-memory-quality-control skill remains the branch-accuracy drift detector; the c-11-memory-carryover-from-branch skill only imports richer memory whose code validity has been proven or explicitly approved.