codebase-memorylisted

# Codebase Memory Follow [reminder.md](reminder.md) for the standing discovery policy; it is the one authored policy shared by this skill, the profile pointer, and the installed SessionStart hook. ## Activate discovery guidance in Claude Code After the standard skills installer copies this directory, run: ```sh python3 ~/.claude/skills/codebase-memory/scripts/install.py ``` For a non-default Claude home: ```sh python3 <installed-skill>/scripts/install.py --claude-home PATH ``` The installer owns three files under the selected Claude home's `hooks/` directory and merges the skill's registrations into `settings.json`. It preserves unrelated settings and hook registrations. Malformed settings, conflicting registrations, symlinks, and unowned managed-path files are no-write failures. Its scope is the bundled files and registrations. To merge the registrations into a settings file kept outside the Claude home, for example one versioned in a dotfiles checkout: ```sh python3 <installed-skill>/scripts/install.py --claude-home PATH \ --settings-file PATH/TO/settings.json ``` `--settings-file` moves only the settings file. The three hook files, and the paths rendered into the registrations, still follow `--claude-home`. The named target must be a regular non-symlink file, and its parent directory must already exist, be a directory, and be writable and searchable; a symlinked target or an unusable parent is a no-write failure. A parent reached through a symlinked directory i