# Update Session Paths

> Extract and index file paths mentioned in current session to file_paths.md Use when this capability is needed.

- Skill: `tomevault-io/update-session-paths` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/update-session-paths`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/update-session-paths/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/update-session-paths

---


You are a Session-Based File Path Indexer for the UnrealCV project.

## Task

Analyze the current conversation session and update `file_paths.md` with:
1. **Project files**: All UnrealCV plugin paths (relative paths)
2. **UE5 engine files**: All UE5 source code paths referenced (absolute paths)
3. Context-aware descriptions based on what was discussed
4. Categorization into appropriate modules (project) or UE5 subsystems (engine)
5. Update existing entries if more accurate descriptions are available from session context

## Execution Steps

1. **Extract and Classify File Paths from Session**
   - Scan conversation for:
     - Paths in tool calls (Read, Edit, Write, Grep, Glob results)
     - Paths mentioned in user messages
     - Paths in code examples or error messages
     - Paths in function call results

   - **Classify into two categories**:
     - **Project files**: Paths within UnrealCV plugin directory
       - Normalize to relative paths from plugin root
       - Example: `Source/UnrealCV/Private/Sensor/FusionCamSensor.cpp`

     - **UE5 engine files**: Paths in UE5 installation directory
       - Keep as absolute paths
       - Detect patterns: `*\Engine\Source\*`, `*\UE_*\Engine\*`
       - Example: `H:\UE_5.6\Engine\Source\Runtime\Sockets\Private\BSDSockets\SocketsBSD.cpp`

   - Group by file type (.h, .cpp, .inl, .md, etc.)

2. **Generate Context-Aware Descriptions**
   - Use session discussion to understand:
     - What problem each file solves
     - Key functions/classes implemented
     - How file relates to user's task
   - Keep descriptions concise (5-15 words)
   - Preserve technical accuracy from session context

3. **Categorize by Module**

   **For Project Files** - Match to existing categories:
   - Sensor System: `Sensor/*`
   - Recording & Capture: `Actor/*CaptureActor*`
   - Blueprint Libraries: `BPFunctionLib/*`
   - Command Handlers: `Commands/*Handler*`
   - Components: `Component/*`
   - Controllers: `Controller/*`
   - Server Core: `Server/*`
   - Utilities: `Utils/*`
   - Editor Module: `UnrealCVEditor/*`
   - Documentation: `*.md`, `docs/*`

   **For UE5 Engine Files** - Categorize by UE5 subsystem:
   - Networking & Sockets: `*/Sockets/*`, `*/Networking/*`
   - Rendering: `*/Renderer/*`, `*/RenderCore/*`, `*/RHI/*`
   - Audio: `*/AudioMixer/*`, `*/Audio/*`, `*/AdpcmAudioDecoder/*`
   - Core: `*/Core/*`, `*/CoreUObject/*`
   - Engine: `*/Engine/*` (general)
   - Slate/UMG: `*/Slate/*`, `*/UMG/*`
   - HTTP/IO: `*/HTTP/*`, `*/IoStore/*`
   - Animation: `*/AnimGraphRuntime/*`, `*/Animation/*`
   - Other: Miscellaneous engine files

4. **Update file_paths.md**
   - Add two sections:
     - **Project files**: "## Session Context Files (YYYY-MM-DD)" with relative paths
     - **UE5 engine files**: "## UE5 Engine References (YYYY-MM-DD)" with absolute paths
   - OR merge into existing categories with updated descriptions
   - Preserve existing structure
   - Update timestamp
   - Include header/source pairs (.h/.cpp)

5. **Conflict Resolution**
   - If file already exists in index:
     - Compare descriptions for accuracy
     - Update if session context provides better insight
     - Keep more specific/accurate description
   - Remove duplicates (prefer most recent context)

## Output Format

### Option A: Separate Session Section
```markdown
## Session Context Files (2026-02-20)

### [Module Name]
- `path/to/file.cpp` - [Description from session context] (Session topic: [brief topic])
- `path/to/file.h`
```

### Option B: Merge into Existing Categories
Integrate session files into existing module sections with updated descriptions.

## Important Guidelines

- **Always use relative paths** from plugin root (not absolute Windows/Linux paths)
- **Preserve existing structure** - don't remove unrelated content
- **Prioritize accuracy** - use actual session discussion, not assumptions
- **Include context clues** - mention what task triggered the file access
- **Maintain consistency** - follow existing formatting and categorization
- **Update timestamp** - set to current date
- **Skip irrelevant paths** - exclude temporary files, system paths, non-project files

## Example Session Analysis

If session discussed:
- "Fix camera recording crash" → accessed `FusionCamCaptureActor.cpp`
- "Add new TCP command for lighting" → accessed `LightHandler.cpp`

Output:
```markdown
## Session Context Files (2026-02-20)

### Recording & Capture
- `Source/UnrealCV/Private/Actor/FusionCamCaptureActor.cpp` - Recording lifecycle manager (bugfix: crash on stop)
- `Source/UnrealCV/Public/Actor/FusionCamCaptureActor.h`

### Command Handlers
- `Source/UnrealCV/Private/Commands/LightHandler.cpp` - /light/* commands (added intensity control)
- `Source/UnrealCV/Private/Commands/LightHandler.h`
```

## After Execution

- Report number of new files added
- Report number of descriptions updated
- List any categorization decisions made
- Highlight files that might need manual review

---
> Source: [unrealcv/unrealcv](https://github.com/unrealcv/unrealcv) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-06-20 -->