ticket-knowledge-logger

Automate ticket investigation logging into structured documentation with directory generation.

Updated Aug 27, 2026

Search Tags:#automation #workflow #documentation #logging #jira #ticket #knowledge-base

Ready to run

npx skills add https://github.com/octkp/dotfiles --skill ticket-knowledge-logger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ticket-knowledge-logger
Source: https://github.com/octkp/dotfiles/tree/main/claude/skills/ticket-knowledge-logger
Command: npx skills add https://github.com/octkp/dotfiles --skill ticket-knowledge-logger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

チケット調査・実装に関する会話ログと要点を一元管理し、ナレッジを蓄積する作業を自動化します。

Core Features & Use Cases

会話ログと要約の自動作成と保存
チケット番号とカテゴリを基にした整理されたディレクトリ構造の生成
Jira のチケット名を取得して、わかりやすいディレクトリ名を付与

Quick Start

新しいチケットの会話ログと要約を作成して保存してください。

Frequently Asked Questions about ticket-knowledge-logger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automatically log Jira ticket conversations and summaries into documentation?▼

You can automatically log Jira ticket conversations by using a workflow that generates a structured directory, creates LOG.md and README.md files, and optionally retrieves the Jira ticket name from its URL to organize knowledge summaries.

What is the best way to structure knowledge base directories for ticket investigations?▼

Structuring knowledge base directories for ticket investigations is best handled by generating an organized folder structure based on the ticket number and category, then storing conversation logs and summaries inside dedicated LOG.md and README.md files.

Can I retrieve the Jira ticket name from a URL to name my documentation folders?▼

Yes, retrieving the Jira ticket name from a URL to name documentation folders is supported as an optional step within the logging workflow, ensuring directories have clear and recognizable names for audits and onboarding.

How do I create structured documentation from ticket chats for team onboarding?▼

Creating structured documentation from ticket chats for onboarding involves capturing investigation and implementation conversations, then automatically saving them with summaries into a defined directory structure with LOG.md and README.md files.

Do I need any external dependencies to automate ticket logging and summary creation?▼

No external dependencies are required to automate ticket logging and summary creation, as the workflow operates independently to generate directories and documentation files directly from your ticket conversations.

When should I use an automated workflow for logging ticket chats and knowledge summaries?▼

You should use an automated workflow for logging ticket chats and knowledge summaries when your team needs to capture Jira ticket details and chat transcripts centrally for audits, compliance, or onboarding purposes.