Where does the skill save the troubleshooting logs?

All logs are automatically saved as markdown files in the `docs/troubleshooting/` directory of your project, using a YYYY-MM-DD-title.md naming convention.

What language are the logs generated in?

The current template generates detailed troubleshooting documents in Korean, making it ideal for Korean-speaking development teams.

Why is the 5 Whys technique included?

The 5 Whys technique is included to help developers move beyond surface-level fixes and identify the actual root cause to prevent the issue from happening again.

Can I manually trigger a log if Claude doesn't suggest it?

Yes, you can manually trigger the skill at any time by typing `/troubleshoot-logger:log` followed by an optional title in the terminal.

Does it include code snippets in the logs?

Yes, the writing guidelines instruct the skill to include specific code blocks, commands, and error messages rather than abstract descriptions.

Troubleshoot Logger

Name: Troubleshoot Logger
Author: gitjay3

bygitjay3

•

Analytics & Monitoring

Automates the documentation of bug fixes and troubleshooting sessions using the STAR method and root cause analysis.

Troubleshoot Logger is a specialized Claude Code skill designed to streamline technical documentation by automatically recording problem-solving sessions. It follows the STAR (Situation, Task, Action, Result) methodology and incorporates a 5 Whys root cause analysis to ensure deep understanding and prevent issue recurrence. By organizing logs in a standardized markdown format within a dedicated documentation directory, it helps teams build a searchable knowledge base of technical debt resolutions and debugging patterns directly from their terminal sessions.

Key Features

01Context-Aware Documentation: Automatically pulls specific code changes, commands, and error messages from the active session.

02Automated File Management: Creates standardized, timestamped markdown files in the docs/troubleshooting/ directory.

032 GitHub stars

04STAR Method Integration: Structures logs using Situation, Task, Action, and Result for clear context.

05Root Cause Analysis: Implements the 5 Whys technique to identify and document the underlying source of bugs.

06Prevention Planning: Includes a dedicated section for tracking action items to prevent bug recurrence.

Use Cases

01Onboarding new developers by providing a chronological history of past technical challenges and their solutions.

02Documenting complex API latency issues or database performance bottlenecks for future team reference.

03Building a searchable internal wiki of resolved bugs and their specific prevention strategies.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add gitjay3/self-made-skills log

For use in Claude.ai and ChatGPT

Download Skill