# Agentic Memory Maintain

> Maintain existing docs/solutions/ knowledge by wrapping the imported agentic-memory-refresh skill without modifying imported knowledge-plugin skills.

- Skill: `dolphinai2026/agentic-memory-maintain` (Agent Skill)
- Install (CLI): `npx skillmds@latest add dolphinai2026/agentic-memory-maintain`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dolphinai2026/agentic-memory-maintain/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: dolphinai2026 (https://skillmd.com/u/dolphinai2026)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/dolphinai2026/agentic-memory-maintain

---


# Agentic Memory Maintain Adapter

Use this skill when refreshing, consolidating, or pruning existing knowledge in
`docs/solutions/`, including when `agentic-memory-compound` output suggests an
older learning may now be stale.

This is an Agentic Coding owned adapter. Do not edit imported skills:

- `agentic-memory-compound`
- `agentic-memory-refresh`
- `agentic-memory-sessions`

## Workflow

1. Invoke the imported `agentic-memory-refresh` skill, passing through all
   arguments, including `mode:headless` when present.
2. Enforce the target project's solution path contract on every file the
   refresh moves, merges, or rewrites. In this repository every output must
   stay under `docs/solutions/{level}/{module}/{filename}.md`; do not create
   `docs/solutions/<category>/` paths.
3. After refresh writes complete, if the current directory is a Git-managed
   repository, auto-commit knowledge outputs before the final report:
   - Commit only repo-local knowledge files changed by this refresh, normally
     files under `docs/solutions/`.
   - Confirm each staged path is inside the current repository before staging.
   - Use `git add -- <path...>` and then `git commit` with a concise docs
     message such as `docs: refresh agentic memory knowledge`.
   - Do not push. Do not merge. Do not stage unrelated files.
   - If no repo-local knowledge files changed, the directory is not
     Git-managed, or the changed paths cannot be safely attributed to this
     refresh, skip the commit and include the reason in the report.

## Output

End with:

- refreshed, consolidated, or deleted file path(s), or a statement that no
  changes were needed;
- whether the repo-local knowledge files were auto-committed or why the skill
  skipped the commit.