Write Agent Memory System Review

Use this local skill to write or update type: kb/agent-memory-systems/types/agent-memory-system-review.md notes for external systems under kb/agent-memory-systems/reviews/.

This is a local commonplace-repo workflow, not a promoted cp-skill-* framework skill. The parent agent owns GitHub handling, local source directory setup, artifact lifecycle, QA, validation, indexes, and the final report. Delegate the code-grounded review drafting to a fresh worker context whenever the harness has a sub-agent mechanism.

Delegation means a harness-provided sub-agent/worker tool only. Never start a nested agent by running codex, codex exec, claude, or any other agent CLI from the shell. If the current agent cannot access the required harness sub-agent tool or an agent slot is unavailable, stop or wait and report the blocking condition; do not work around the limit with a command-line agent process.

Prerequisites

• The topic is a GitHub repository reference: owner/repo or https://github.com/owner/repo.
• The repository is reachable.
• The checkout lives under related-systems/, outside kb/.

If the system has no reachable source code, stop and write a lightweight note instead.

Steps

1. Normalize the repository target. Derive:

• repo_url - canonical full GitHub repository URL for citations, https://github.com/{owner}/{repo} with no trailing slash or .git
• owner - GitHub owner or organization
• repo_name - final path segment
• repo_slug - default review slug, usually repo_name
• checkout_slug - owner-qualified checkout slug: {owner}--{repo_name}
• checkout_dir - related-systems/{checkout_slug}/
• source_dir - same path as checkout_dir; this is the directory passed to the review type contract
• note_path - kb/agent-memory-systems/reviews/{repo_slug}.md

1. Resolve same-name collisions. Use the repository name as the default review filename unless there is already an established house-style variant. If kb/agent-memory-systems/reviews/{repo_name}.md already exists for a different GitHub repository with the same final path segment, use kb/agent-memory-systems/reviews/{owner}--{repo_name}.md. Do not overwrite or update a same-name review unless its **Repository:** line or frontmatter resolves to the same owner/repo.

1. Choose the checkout path. Use the owner-qualified checkout directory for new clones. Existing reviews may have legacy basename-only checkouts such as related-systems/{repo_name}/; use a legacy checkout only when its origin remote resolves to the same GitHub owner/repo you are reviewing. If a legacy checkout points to a different owner with the same repository name, do not pull it, delete it, or repurpose it; clone the requested repo into the owner-qualified checkout_dir.

1. Check main repo state. Run git status --short in the main repo before cloning or writing so you know whether unrelated changes already exist.

1. Clone or refresh. Run checkout-local git commands from checkout_dir using the Bash working directory, a subshell, or cd first. Do not spell checkout-local commands as git -C "{checkout_dir}" ...; permission rules match command prefixes such as git fetch, and git -C ... fetch can unnecessarily trigger approval prompts. After checkout git operations, return to the Commonplace root before metadata capture, archive moves, index refresh, QA, or validation.

If checkout_dir does not exist:

   git clone "{repo_url}" "{checkout_dir}"

If checkout_dir exists:

   (
     cd "{checkout_dir}"
     git fetch --all --prune
     git status --short
     git merge --ff-only @{upstream}
   )

If using cd in the current shell instead of a subshell, save the Commonplace root first and cd back to it immediately after the checkout git commands.

Use git fetch rather than git pull so the refresh uses the agent-approved fetch permission path. If the merge cannot fast-forward because of local commits or conflicts, stop and report the state. Do not force, delete, or overwrite an existing checkout.

1. Capture source metadata. Record the top-level listing, most recent commit, README, and package/manifest files for the writer's context. The parent establishes GitHub-specific metadata before delegation:

• source_dir: checkout_dir
• source_url: repo_url
• reviewed_commit: output of git rev-parse HEAD run from checkout_dir
• commit_url: {repo_url}/commit/{reviewed_commit}
• citation format:
• files: {repo_url}/blob/{reviewed_commit}/{path}
• directories: {repo_url}/tree/{reviewed_commit}/{path}

Write the refresh marker immediately after a successful clone or fetch-and-fast-forward:

   (
     cd "{checkout_dir}"
     git_dir="$(git rev-parse --absolute-git-dir)"
     date -Iseconds > "$git_dir/commonplace-checkout-refreshed-at"
   )

If the marker is more than 1 hour old by the time drafting starts, carry a checkout freshness warning into the final report. If it is more than 24 hours old, refresh again before drafting.

1. Archive an existing review before writing. If note_path exists, archive it before drafting or delegating:

   git mv "{note_path}" "{note_path%.md}.replaced.{YYYY-MM-DD}.md"

Then mark the archived file:

• Set status: outdated in frontmatter.
• Set tags: [] (clearing any trace-derived tag).
• Add after the title: > Replaced {YYYY-MM-DD}. See [{name}](./{name}.md) for the current review.

Do not read the archived .replaced.*.md file while writing the replacement.

1. Draft the review by delegation. Use kb/agent-memory-systems/types/agent-memory-system-review.md as the worker's artifact contract. Its embedded comparison lens is the review-time distillation of the memory-system design; do not ask the worker to load the full design note during ordinary review writing. The worker should follow the type contract's current retained-artifact vocabulary, including knowledge-artifact and system-definition-artifact use as behavioral-authority families.

Launch one fresh sub-agent or worker with a minimal task-local context. Do not fork the parent's full context when the harness offers a clean-context option. Give the worker only the local skill handoff, the type contract path, the source directory, the target note path, and the source metadata listed below. Use only the harness sub-agent mechanism for this delegation; do not launch an agent CLI from Bash.

The worker has only this ownership:

• read kb/agent-memory-systems/COLLECTION.md
• read kb/agent-memory-systems/types/agent-memory-system-review.md
• read 1-2 current reviews for style
• inspect source_dir
• write note_path
• decide trace-derived status from implementation evidence and either include both the placement section and trace-derived tag, or omit both

Pass the worker the inputs defined in the type contract's ## Inputs section — the contract is authoritative; read the list from there (currently source_dir and note_path).

Also pass this parent-supplied source metadata for the review note:

• source_url
• reviewed_commit
• commit_url
• citation format for files and directories

The worker must not edit indexes, archived reviews, the trace-derived survey, checkout state, or unrelated files. The worker must not spawn further agents unless the harness exposes a proper sub-agent tool in that worker context; if it needs a nested worker and no slot/tool is available, it must pause and report the wait/blocker. It must never use codex, codex exec, claude, or similar shell commands as a substitute. The parent owns checkout, archive moves, curated index edits, taxonomy QA, semantic QA, validation, and final report.

If the harness cannot launch a sub-agent or worker, stop after setup and report that delegated drafting is unavailable. Do not draft locally unless the user explicitly authorizes a local fallback for this run. If the user authorizes that fallback, report drafting was local, not delegated as a workflow exception.

1. Update the README only if needed. Only edit kb/agent-memory-systems/README.md when:

• the system was named in the ## Coverage "Review backlog" callout — remove it there, or
• the repo adds a genuinely new cross-system pattern worth a line in ## Patterns Across Systems.

Keep the edit minimal and specific.

1. Update the trace-derived survey if needed. If the review's trace-derived placement adds meaningfully to the survey, update kb/agent-memory-systems/trace-derived-learning-techniques-in-related-systems.md.

1. Run taxonomy QA. Re-read the drafted review and check whether it makes the artifact contract clear where relevant. Work from the type contract's artifact-analysis field list (plus its trace-derived split, when the system learns from traces) — the contract is authoritative for which fields exist and what each means; do not QA against a remembered list. For each contract field, ask: does the review make that mechanism clear where it affects the comparison? Do not force a rigid section into every review; add or revise prose only when the existing text leaves a mechanism ambiguous.

If a field is absent because the reviewed system has no distinctive mechanism there, leave it absent. If the absence hides an important tradeoff, fix the review before semantic QA.

1. Run semantic QA. Run the live-agent procedure from kb/instructions/run-review-batches-on-note.md on the new review note using the semantic bundle: create the runs and prompts with commonplace-create-review-runs, delegate each returned run to a sub-agent, then ingest each sentinel-bracketed output with commonplace-ingest-bundle-output. Treat it as a read-only QA loop: extract findings, fix clearly valid issues, and leave uncertain findings for the final report rather than forcing a rewrite.

Do not use commonplace-run-review-bundles for this skill workflow unless the user explicitly authorizes subprocess runner execution, because that command invokes claude or codex exec internally. If semantic QA cannot be completed through the current harness, report it as a blocked QA step rather than substituting a shell-launched agent.

1. Validate. Run:

    commonplace-validate "{note_path}"

If validation reports structural or description-quality issues, fix them and validate once more.

Report

Report:

• repo cloned or reused
• checkout freshness warning, if any
• review path
• whether drafting was delegated
• whether the curated index changed
• whether trace-derived-learning-techniques-in-related-systems.md changed
• taxonomy QA outcome
• semantic gate bundle outcome
• final commonplace-validate result

Constraints

Always:

• keep checkouts under related-systems/
• use owner-qualified checkout directories for new clones
• write reviews under kb/agent-memory-systems/reviews/
• cite repo source files with GitHub URLs pinned to the commit derived from the checkout
• run semantic QA before final validation

Never:

• put checked-out repos under kb/
• overwrite or repurpose an existing checkout whose remote points to a different owner/repo
• force-pull, delete, or reset a checkout to handle conflicts
• run codex, codex exec, claude, or another agent CLI from the shell to bypass delegation or worker limits
• use commonplace-run-review-bundles in this workflow without explicit authorization for its subprocess runner
• leave the review unvalidated