{
  "markdown": "# conversation-log\n\nA Claude Code skill that automatically detects conversations and saves them as structured Markdown log files.\n\n## Why This Exists\n\nClaude Code sessions are used for all kinds of work — development, business discussions, strategy consultations, support follow-ups, and more. Those exchanges vanish when the session ends or when context compression kicks in during long sessions, leaving no record of decisions made, actions agreed upon, or messages drafted.\n\n**conversation-log** solves this by detecting substantive conversations and prompting you to save them before they disappear. It covers **all** conversation types — development discussions, business calls, and everything in between.\n\n## Installation\n\n### Quick Install\n\n```bash\n# 1. Clone the repository\ngit clone https://github.com/aliksir/conversation-log /tmp/conversation-log\n\n# 2. Install the skill\nmkdir -p ~/.claude/skills/conversation-log\ncp /tmp/conversation-log/skills/conversation-log.md ~/.claude/skills/conversation-log/SKILL.md\n\n# 3. Install the auto-detection rule (optional but recommended)\nmkdir -p ~/.claude/rules\ncp /tmp/conversation-log/rules/auto-detect-chat.md ~/.claude/rules/auto-detect-chat.md\n\n# 4. Clean up\nrm -rf /tmp/conversation-log\n```\n\nAfter installation:\n- The `/conversation-log` slash command becomes available in all sessions\n- If the rule is installed, Claude will automatically suggest saving conversations at natural break points\n\n## Usage\n\n### Automatic Detection\n\nWhen the auto-detection rule is installed, Claude monitors your conversation in the background. When it detects a qualifying exchange (3+ turns, substantive content), it will suggest saving a log at a natural break point:\n\n> \"会話が長くなってきたので、ここまでのログを保存しますか？ `/conversation-log` を実行します。\"\n\nIt also proactively suggests saving when:\n\n- **Volume trigger**: The conversation reaches ~20 round-trips (to prevent context compression loss)\n- **Phase transition**: The conversation shifts topics (e.g., chat → development)\n- **Session end**: Before `/handover` or session wrap-up\n\n### Manual Invocation\n\nYou can also trigger logging at any time:\n\n```\n/conversation-log\n```\n\nNo arguments needed. The skill scans the current conversation, identifies topics, and writes one Markdown file per topic.\n\n### Append Mode\n\nIf you run `/conversation-log` multiple times in the same session on the same topic, it **appends** to the existing file rather than creating a new one. This ensures a single continuous log per topic per day, even across multiple save points.\n\n### Session-End Auto-Run\n\nTo automatically run `/conversation-log` before your session handover, add this to your `CLAUDE.md` or memory:\n\n```yaml\nsession:\n  end: [\"/conversation-log\", \"/handover\"]\n  auto_approve: [\"/conversation-log\", \"/handover\"]\n```\n\nThis ensures conversations are captured before the session context is lost.\n\n## Saved File Format\n\nLogs are saved to `chat-logs/` in your working directory using the naming pattern:\n\n```\nchat-logs/YYYYMMDD_{topic-name}.md\n```\n\nMultiple distinct topics on the same day get separate files: `_2.md`, `_3.md`, etc.\n\nEach file contains:\n\n```markdown\n# 会話ログ: {トピック}\n\n| 項目 | 内容 |\n|------|------|\n| 日時 | YYYY-MM-DD HH:MM |\n| カテゴリ | business / support / consultation / decision / development / other |\n| 関連先 | {company / service / person} |\n\n## 要約\n3–5 line summary of what was discussed.\n\n## 会話の流れ\n**User**: What the user said, asked, or provided\n**Assistant**: What was proposed, drafted, or answered\n**User**: Follow-up, decisions, additional context\n...\n(Full chronological record — not summarized)\n\n## 主要な決定事項\n- Key decisions or agreements\n\n## 送付・作成した文面\n> Any messages or documents drafted during the conversation (omitted if none)\n\n## 次のアクション\n- [ ] Follow-up tasks\n```\n\n## Categories\n\n| Category | When to use |\n|----------|-------------|\n| `business` | Contracts, billing, negotiations, vendor or partner relations |\n| `support` | Account issues, application procedures, service requests |\n| `consultation` | Technical advice, strategy discussions, architecture guidance |\n| `decision` | Choices made, options evaluated, direction established |\n| `development` | Feature implementation, bug fixes, code reviews, refactoring, infrastructure changes |\n| `other` | Substantive exchanges that don't fit the above |\n\n## Configuration\n\n### Changing the Save Directory\n\nThe default save location is `chat-logs/` relative to your working directory. To change it, edit the path in `skills/conversation-log.md`:\n\n```markdown\n# Default\nchat-logs/YYYYMMDD_{topic-name}.md\n\n# Example: save to home directory\n~/.claude/chat-logs/YYYYMMDD_{topic-name}.md\n\n# Example: project subfolder\ndocs/conversations/YYYYMMDD_{topic-name}.md\n```\n\nAlternatively, add this to your project's `CLAUDE.md` to override per-project:\n\n```markdown\n## conversation-log settings\nconversation_log_dir: \"~/my-chat-logs\"\n```\n\n### Uninstalling\n\n```bash\n# Remove the skill\nrm -rf ~/.claude/skills/conversation-log\n\n# Remove the auto-detection rule\nrm ~/.claude/rules/auto-detect-chat.md\n```\n\n### Disabling Auto-Detection Only\n\nTo turn off automatic prompts while keeping the `/conversation-log` command available, remove the rule file:\n\n```bash\nrm ~/.claude/rules/auto-detect-chat.md\n```\n\n## Language\n\n- Log output format uses Japanese section headers (会話ログ, 要約, etc.)\n- [Japanese README](README.ja.md) is also available\n\n## License\n\nGPL-3.0 — see [LICENSE](LICENSE) for details.\n",
  "bytes": 5415,
  "sha": "9b16c7701ba3e96fbbfb6cd34d5f92df06ed30f3919a5d64c14276513a97a299",
  "repo_slug": "aliksir/conversation-log",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_aliksir_conversation_log_conversation_lo_8c8f356b/readme"
}