Skip to content
Back to skills

Daf Read Conversation

ASecurity

Read the conversation history from another repository in this multi-project session

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 29, 2026
developmentbashgitapifrontendbackend

Works with

  • claude code
  • api

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add itdove/devaiflow --skill daf-read-conversation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Daf Read Conversation?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Daf Read Conversation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/itdove-daf-read-conversation/badge)](https://www.skillsdirectory.com/skills/itdove-daf-read-conversation)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: daf-read-conversation
description: Read the conversation history from another repository in this multi-project session
user-invocable: true
argument-hint: "[CONVERSATION-UUID]"
---

Read the conversation history from another repository in this multi-project session to understand work done in related codebases.

USAGE:
1. First, run `/daf list-conversations` to see all available conversations
2. Then use this command to read a specific conversation's history

IMPORTANT: You can only read conversations from OTHER repositories, NOT the current one. Reading the current conversation would duplicate the context you already have.

To read a conversation:

```bash
# Get session info to find conversation details
daf info

# The output shows all conversations with their:
# - Working directory name (e.g., "backend-api", "frontend-ui")
# - Repository name
# - Agent session ID
# - Git branch

# Read the conversation using the session ID and storage format reported by
# `daf info`. Conversation files are backend-specific. For Claude Code they
# are stored at: ~/.claude/projects/<encoded-path>/<uuid>.jsonl

# Example workflow:
# 1. Get the session UUID for the conversation you want to read
# 2. Find the encoded path for that repository
# 3. Read the .jsonl file

# Note: The .jsonl file contains the full conversation history in JSON Lines format
# Each line is a JSON object representing one message in the conversation
```

MULTI-CHOICE SELECTION:
If there are multiple conversations in this session, you can provide a multi-choice interface:

1. List all conversations EXCEPT the current one
2. User selects which conversation to read
3. You read that conversation's .jsonl file

WHAT TO LOOK FOR:
When reading another conversation, focus on:
- What features were implemented
- API contracts or interfaces defined
- Data models or schemas created
- Configuration changes made
- Dependencies or integration points
- Decisions about implementation approach

This helps maintain consistency across the multi-repository feature implementation.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.