Codebase Memory Capture and Wiki Compilation
Capture session lessons, compile a linked codebase wiki, and retrieve guidance with evidence and explicit freshness checks.
Before & after
Same prompt, same agent — the only difference is the skill.
That's a good question. Most teams rely on git commit messages or documentation wikis, but those get outdated fast. You could set up a decision log or read through your PRs from that time period. Some teams use architecture decision records, or ADRs, to formally document why they made choices. You'd need to decide what decisions matter enough to capture, and then someone has to write and maintain that documentation. It's hard to keep it current unless you build it into your workflow somehow.
CODEBASE MEMORY SYSTEM (auto-compiled) SESSION-START HOOK → Loads agents.md (active decision-makers, CTO priorities) + index.md (compiled concepts wiki) → Runs at every session start; you see relevant architectural context before you code AUTO-CAPTURED (per session) → Session SDK logs end-of-session Claude summary: "Architecture questions answered today: X vs. Y trade-off, reason we chose Z" → Daily log saved to logs/2026-07-31.md (session summary + decisions made) WIKI PROMOTION (nightly flush) → Last 7 days of daily logs → concepts and connections wiki (Obsidian) → Example: "Why we chose Postgres over DynamoDB" promoted as a permanent wiki entry → Backlinks auto-added: "Postgres decision" links to "scaling strategy", "transaction guarantees", "team SQL expertise" QUERY FROM MEMORY (instant) Asked: "How did we justify the auth refactor last quarter?" Clause answers in 3 sec: "See kb/auth-refactor-decision.md (May 2026); context was security audit X and team capacity Z; alternative we considered was Y. Linked issues: security-audit-5, sprint-23, onboarding-refactor." OBSIDIAN GRAPH VIEW → See your architectural concepts as a visual network → "Data layer" connects to "caching strategy", "backup procedures", "API contracts" → Hover over nodes to see decision timeline CUSOMIZATION vault_root: /your-repo/.claude-memory log_retention: 30 days before wiki promotion flush_frequency: Nightly at midnight UTC hook_prompts: Tuned to ask about trade-offs and alternatives codebase_scope: This repo + shared monorepo (if applicable) RESULT: New engineer onboarding cut from 2 weeks to 4 days (can query the memory instead of code archaeology)
About this skill
“Why am I explaining this repository again?” Session summaries rarely solve the problem: they bury useful lessons in chronology and preserve assumptions after the code changes. This workflow turns specific discoveries into a compact, linked codebase wiki with evidence, scope, and a way to check whether each lesson still holds.
What it does
- Captures decisions, debugging discoveries, failed approaches, and unfinished work as distinct session records.
- Promotes supported lessons into topic pages while keeping hypotheses and temporary handoffs separate.
- Records source paths, revision context, and verification conditions so old advice can be checked efficiently.
- Resolves contradictory entries without silently discarding their history or merging different branch behaviors.
- Retrieves a small set of relevant pages before opening the specific source files needed to confirm current behavior.
- Helps configure session-start, pre-compaction, and session-end capture when the installed Claude Code version supports the required hooks.
What you get
A project memory organized around a compact index, dated session logs, and linked topic pages. For setup requests, Claude creates the authorized project files and provides or implements compatible automation, distinguishing working capture from manual fallbacks.
Best for
Developers returning to the same repositories, teams handing work between sessions, and maintainers tired of rediscovering the same architectural decisions and debugging traps. The wiki uses plain Markdown; Obsidian is optional.
SKILL.md preview
---
name: codebase-memory-capture-and-wiki-compilation
description: Captures codebase lessons as evidence-bearing session records and compiles them into a linked Markdown wiki, using scoped retrieval and targeted source checks to keep guidance current. Use when the user says "set up codebase memory", "I keep reexplaining this repo", "save what we learned", "capture this before compaction", "flush the session logs", "what should I know before touching this module?", or "the wiki keeps giving me stale advice".
---
# Codebase Memory Capture and Wiki Compilation
… (sign up to view the full skill)More development skills
View all Development skills →Performance Bottleneck Profiling: Node, Python, Go
Classifies a slowdown, gives exact profiler commands, reads the output, and proves the fix with same-conditions p95/p99 numbers.
Feature Scaffolding with Working Tests
Turn a short feature spec into code, runnable tests, and integration wiring that match your existing project.
Feature Flag Rollouts and Kill Switches
Design staged flag rollouts, verify rollback paths, and audit flag debt with explicit defaults, gates, and retirement plans.
Microcontroller Firmware and RTOS Engineering
Build and debug MCU firmware with bounded ISR/RTOS timing, safe DMA ownership, and measured power budgets.