skills.rest
Foxfire1st
Foxfire1stCOMMUNITY
Explore all skills by this author →
GitHub

c-11-memory-carryover-from-branch

Carry verified onboarding memory from a source branch after code lands.

27|4|Updated Mar 21, 2026
Search Tags:#onboarding#verification#branching#memory#code-review#memory-carryover
One-click install
npx skills add https://github.com/Foxfire1st/agents-remember --skill c-11-memory-carryover-from-branch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: c-11-memory-carryover-from-branch
Source: https://github.com/Foxfire1st/agents-remember/tree/main/.cursor/skills/c-11-memory-carryover-from-branch
Command: npx skills add https://github.com/Foxfire1st/agents-remember --skill c-11-memory-carryover-from-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Carry richer onboarding memory from a source branch into official memory only when the corresponding code has landed on the official branch. This ensures memory does not precede code changes and stays in sync with the verified codebase.

Core Features & Use Cases

  • Selective memory reconciliation: prove which source-branch notes exist on the official branch, and carry only the corresponding onboarding into official memory.
  • Verification-driven: re-base carried onboarding to the official code commit and refresh verification metadata against landed changes.
  • Safe workflows: supports different candidate kinds (file-sidecar, route-overview, memory-only-doc, entity-catalog) with strict rules to avoid auto-carry of unlanded or divergent memory.

Quick Start

Run memory_carryover_plan to generate a dry-run and then, after review, run memory_carryover_apply to execute the chosen carryover.

Frequently Asked Questions about c-11-memory-carryover-from-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I carry onboarding memory from a feature branch to the official branch?▼

Carry onboarding memory by running memory_carryover_plan to generate a dry-run, reviewing the output, and executing memory_carryover_apply. This ensures memory reconciliation happens only after the corresponding code has officially landed.

What verification checks are required for memory carryover from branches?▼

Memory carryover requires evidence-based checks such as exact-landed-commit, patch-id-match, and final-content-match. These verifications prove the source-branch code exists on the official branch before carrying the corresponding onboarding memory.

Can I automatically sync all per-file notes and route overviews from a feature branch?▼

No, automatic carryover of unlanded or divergent memory is blocked by strict rules. The workflow selectively reconciles candidate kinds like file-sidecar, route-overview, memory-only-doc, and entity-catalog only after verifying the code has landed.

Why does onboarding memory go out of sync with the verified codebase?▼

Onboarding memory goes out of sync when it precedes code changes on the official branch. The memory carryover workflow prevents this by re-basing carried notes to the official code commit and refreshing verification metadata against the actual landed changes.

What is the best way to reconcile entity catalogs between feature branches and the official codebase?▼

The best way to reconcile entity catalogs is using a verification-driven workflow that proves the source-branch code has landed on the official branch, then selectively carries the corresponding memory to keep everything in sync.

Related Skills

Explore More Software Engineering Skills→
sheehesheehe

do

Coordinate phased project execution with subagents, verification, and branch-sync handoffs.

Community
Advanced
vyayasanvyayasan
53

refresh

Re-run onboarding due diligence searches to detect material changes in customer risk profiles.

Community
Advanced
jwmossmozjwmossmoz
3

lando

Polls the Lango API to determine landing job statuses and outcomes.

Community
Basic
twikustwikus
3

sync-with-claude

Synchronize local ~/.claude configuration folders to the repository with rsync --delete.

Community
Intermediate