skills.rest
IBM
IBMOFFICIAL
Explore all skills by this author →
Website𝕏@ibmdeveloperGitHub

di-agent-bug-report

Create Markdown bug reports for IBM watsonx.data integration sessions.

3|Updated May 1, 2026
Search Tags:#transcript#integration#bug report#diagnostics#redaction#session capture#watsonx.data
One-click install
npx skills add https://github.com/IBM/ibm-watsonx-data-integration-skills --skill di-agent-bug-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: di-agent-bug-report
Source: https://github.com/IBM/ibm-watsonx-data-integration-skills/tree/main/agent/skills/di-agent-bug-report
Command: npx skills add https://github.com/IBM/ibm-watsonx-data-integration-skills --skill di-agent-bug-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a difficult watsonx.data integration session into a structured bug report, so failures, regressions, and surprising outcomes can be shared clearly with the right evidence.

Core Features & Use Cases

  • Session capture: Reconstructs the conversation, tool calls, and relevant session metadata into one chronological report.
  • Diagnostics-aware reporting: Pulls job logs and stored flow code when available so the description reflects what actually happened, not just the final status.
  • Safe reporting: Redacts personal information before writing the report and preserves technical identifiers needed for debugging.
  • Use case: An agent repeatedly fails to build or run a watsonx.data integration flow, then uses this Skill to produce a concise report the authors can investigate.

Quick Start

Ask the assistant to create a bug report for the current watsonx.data integration session.

Frequently Asked Questions about di-agent-bug-report

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

FAQPage Schema
How do I create a bug report for a failed watsonx.data integration session?▼

To create a watsonx.data integration bug report, reconstruct the session chronologically, collect job logs and flow code, redact personal information, and cite transcript evidence in a structured Markdown document. This captures pipeline creation, execution, and debugging failures for investigation.

What is the best way to document watsonx.data pipeline execution failures with diagnostics?▼

Documenting watsonx.data pipeline execution failures requires pulling job logs and stored flow code into a diagnostics-aware report. This ensures the description reflects the actual session events and tool calls rather than just the final status outcome.

Can I safely share watsonx.data integration bug reports without exposing sensitive data?▼

You can safely share watsonx.data integration bug reports by applying PII redaction before writing the document. This process removes personal information while preserving the technical identifiers needed for debugging and session recovery.

Does generating a watsonx.data bug report require transcript session capture?▼

Generating a watsonx.data bug report requires transcript session capture to reconstruct the conversation and tool calls chronologically. This transcript-based evidence citation provides the context needed to understand agent-driven data integration workflow failures.

What limitations exist when reporting agent-driven data integration workflow regressions?▼

A key limitation when reporting agent-driven data integration workflow regressions is the dependence on available job logs and stored flow code. The bug report's diagnostic accuracy relies on successfully reconstructing the session metadata from captured transcripts.

Why does my watsonx.data integration flow fail to produce a concise debugging report?▼

Your watsonx.data integration flow may lack a concise debugging report because session reconstruction and diagnostics collection were not applied. Structuring the transcript evidence and redacting PII produces a shareable Markdown document for authors.

Related Skills

Explore More Data & Analytics Skills→
adbertramadbertram
3

claude-code-sessions-cli

Query and analyze local Claude Code session transcripts for project-specific summaries, tool calls, and subagent activity.

Community
Intermediate
ArabelaTsoArabelaTso
142

issue-report-generator

Generate structured Markdown issue reports from failing test cases.

Community
Intermediate
ReidondReidond

session-retrospective

Analyze Claude Code session history to identify recurring agent behavior problems.

Community
Advanced
mozumasumozumasu
139

markdown-session-format

Standardize Claude Code session logs into a consistent Markdown format.

Community
Basic