skills.rest
son-nguyen-301
son-nguyen-301COMMUNITY
Explore all skills by this author →
GitHub

read-debug-findings

Retrieve complete debug findings reports by path or ID.

Updated Apr 6, 2026
Search Tags:#debug#workspace#bug-fix#plan-generation#debug-findings#report-reading
One-click install
npx skills add https://github.com/son-nguyen-301/hydra-claude --skill read-debug-findings
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: read-debug-findings
Source: https://github.com/son-nguyen-301/hydra-claude/tree/main/skills/read-debug-findings
Command: npx skills add https://github.com/son-nguyen-301/hydra-claude --skill read-debug-findings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-debug-findings enables loading a full debug findings report by ID or path to support bug-fix planning and review.

Core Features & Use Cases

  • Retrieve a full debug report by absolute path or by ID from the local workspace.
  • If the specified report is missing, present a concise list of the most recent debug reports for user selection.
  • Provide a self-contained report payload suitable for downstream planning or verification steps.

Quick Start

Provide a full path or an ID to retrieve and view the corresponding debug report.

Frequently Asked Questions about read-debug-findings

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

FAQPage Schema
How do I load a debug findings report by ID for bug-fix planning?▼

Load a debug findings report by providing its unique ID to fetch the full content into the current context. The system retrieves the exact findings data from the local Claude workspace to support analysis and plan generation.

What happens if the debug report I want to retrieve is missing?▼

When a specified debug report is missing, the system presents a concise list of the most recent debug reports available in the local workspace. This allows you to select the correct findings payload for your bug-fix workflow.

Can I use an absolute file path to view debug findings instead of an ID?▼

Yes, you can retrieve debug findings by providing an absolute file path. The system uses the path shell to locate the debug-findings data within the local ~/.claude/projects workspace and loads the complete report.

How do I access local debug findings data for plan generation?▼

Access local debug findings data by requesting a report using either a full path or ID. The system requires access to the ~/.claude/projects workspace to locate and load the self-contained report payload for downstream planning.

Does retrieving a debug report require a specific workspace environment?▼

Yes, retrieving a debug report requires access to the local Claude workspace located under ~/.claude/projects. The system depends on this workspace environment to locate the debug-findings data by path or ID.

What is the best way to review debug findings before starting a bug fix?▼

The best way to review debug findings is to fetch the self-contained report payload by ID or path. This loads the exact findings content into your current context, providing a complete view for analysis and verification before bug-fix planning.

Related Skills

Explore More Software Engineering Skills→
jongwonyjongwony
4

search

Search past Claude Code sessions by keyword and date ranges.

Community
Advanced
jobayerarmanjobayerarman

debugging

Diagnose and fix bugs in the Supplier Management System codebase.

Community
Intermediate
kirvinkirvin

fix-issue

Fetch GitHub issues, analyze code, implement fixes, and run tests.

Community
Intermediate
artk0deartk0de
11

risk-assessment

Analyze codebase risk by cross-referencing git history with semantic search.

Community
Advanced