Skip to main content

conversation-id-generator

Generate a unique conversation ID for orchestrator agents to namespace `.agents/session/*` artifacts and prevent collisions across parallel chats/subagent delegations. Produces an 8-character hex hash from random bytes.

ソース情報

リポジトリ
LumiroCode/copilot-instructions
ソースの最終更新活動
2026年3月29日 14:35
検出された SKILL.md の言語
英語
スター
0
フォーク
0

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

ファイルエクスプローラー
3 ファイル

SKILL.md を表示中

SKILL.md
ソースの指示 · 読み取り専用プレビュー
name
conversation-id-generator
description
Generate a unique conversation ID for orchestrator agents to namespace `.agents/session/*` artifacts and prevent collisions across parallel chats/subagent delegations. Produces an 8-character hex hash from random bytes.
argument-hint
No arguments required
user-invocable
true
metadata
{"skill":"conversation-id-generator","description":"Generate a unique 8-char hex conversation ID from random data to namespace Codex workspace session files files and avoid cross-chat collisions.","usage":"Invoke at conversation start in orchestrator agents before delegating to subagents.","input":"None.","output":"Single 8-character lowercase hexadecimal string."}
# Conversation ID Generator ## When to use - At the start of an orchestrator conversation, before delegating work to subagents. - When any agent needs a unique identifier to tag session memory files (e.g. `plan-<conversationId>.md`, `dod-<conversationId>.md`, `arch-review-<conversationId>.md`) and prevent collisions across parallel chats. - When the orchestrator must communicate to subagents which conversation they belong to. ## Inputs None. The script sources its randomness from `/dev/urandom`. ## Procedure 1. Run the [conversation ID generator script](./scripts/generate_conversation_id.sh): ``` bash codex/skills/conversation-id-generator/scripts/generate_conversation_id.sh ``` 2. Capture the single-line output — an 8-character lowercase hex string. 3. Use the captured value as `<conversationId>` in all session memory file paths for this conversation so files created through the Codex workspace session files tool do not collide with parallel chats. 4. Pass the conversation ID to every subagent invocation so they can read/write the correct session files. ## Output A single line containing an 8-character lowercase hexadecimal string (e.g. `a3f7c012`). ## Completion checks - Output is exactly 8 hex characters (`[0-9a-f]{8}`). - The value is used consistently across all subagent delegations within the conversation. - Session memory files are named with the generated ID (e.g. `.agents/session/plan-a3f7c012.md`).
GitHubで見る