From langchain-pack
Collect LangChain debug evidence for troubleshooting and support. Use when preparing bug reports, collecting traces, or gathering diagnostic information for complex issues. Trigger with phrases like "langchain debug bundle", "langchain diagnostics", "langchain support info", "collect langchain logs", "langchain trace".
How this skill is triggered — by the user, by Claude, or both
Slash command
/langchain-pack:langchain-debug-bundleThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- [Overview](#overview)
Collect comprehensive debug information for LangChain issues including traces, versions, and reproduction steps.
Run pip show on all LangChain packages to gather versions, Python version, and platform info.
Set langchain.debug = True and enable LangSmith tracing. Attach a DebugCallback that logs all LLM start/end/error events with timestamps.
Write a standalone script that reproduces the issue with minimal code and redacted API keys.
Combine environment info, trace logs, and reproduction steps into a debug_bundle.json file.
See detailed implementation for complete debug callback and bundle generator code.
debug_bundle.json with full diagnostic informationminimal_repro.py for issue reproduction| Issue | Cause | Solution |
|---|---|---|
| Callback not capturing | Not attached to LLM | Pass via callbacks= parameter |
| Large trace logs | Long-running operation | Filter by time range |
| API key in logs | Missing redaction | Always redact before sharing |
Basic usage: Apply langchain debug bundle to a standard project setup with default configuration options.
Advanced scenario: Customize langchain debug bundle for production environments with multiple constraints and team-specific requirements.
Use langchain-common-errors for quick fixes or escalate with the bundle.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026
npx claudepluginhub aiminnovations/claude-code-plugins-plus --plugin langchain-pack