Individual skill
docmancer-memory
Recall and write source-attributed local memory.
docmancer/distribution/codex-plugin/skills/docmancer-memory/SKILL.md
Source commit c5c76c69f77b6bfb8b54746f793cb14f8b98293c
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 133
- Repository last updated
- Aug 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- codex Repository topic
- devtool Repository topic
- agent-memory Repository topic
- ai-memory Repository topic
- cli Repository topic
- context-engineering Repository topic
- developer-tools Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# docmancer memory
Docmancer combines curated project Markdown with memory, instructions, and rules discovered from local coding agents.
## Workflow
1. Run `docmancer ask "<the task>" --agent codex` when prior decisions, conventions, or preferences may matter.
2. Follow a cited stable address with `docmancer read <address>` when the complete file or provenance is needed.
3. When the user explicitly asks to remember a durable fact or decision, use `docmancer write` with an explicit project-relative path.
4. Before editing or moving existing memory, read it and pass its current content hash.
5. Use `docmancer import <path>` only when the user asks to copy arbitrary Markdown into the project inbox.
6. Use `docmancer common`, `delivery`, or `timeline` for recurring memory, delivery proof, or canonical decision history.
7. Use `docmancer docs ...` separately for library and vendor documentation.
