pine-debugger

Diagnose and fix errors in Pine Script workflows with debugging tools.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/ainell-owi/LePine --skill pine-debugger-ainell-owi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pine-debugger
Source: https://github.com/ainell-owi/LePine/tree/main/GH%20PINE%20REPOS/pinescript-agents/.claude/skills/pine-debugger
Command: npx skills add https://github.com/ainell-owi/LePine --skill pine-debugger-ainell-owi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pine Script Debugger helps developers diagnose and fix errors, unexpected behavior, and performance bottlenecks in Pine Script when running on TradingView.

Core Features & Use Cases

  • Label-based debugging with on-chart value inspection
  • Table-based monitors for real-time variables
  • Historical value tracking and repainting checks
  • Diagnostics for common Pine Script errors and platform quirks
  • Use across single indicators and complete strategies, including real-time and backtest contexts

Quick Start

Enable the Debug Mode input and apply the provided debugging blocks to begin inspecting values on your chart.

Frequently Asked Questions about pine-debugger

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

FAQPage Schema
How do I debug Pine Script errors in TradingView?

Debug Pine Script errors in TradingView by enabling Debug Mode and applying provided debugging blocks to inspect values directly on your chart. This provides diagnostic guidance for runtime errors and unexpected outputs across both real-time and historical contexts.

Why does my Pine Script strategy output unexpected values during backtesting?

Unexpected Pine Script outputs during backtesting often stem from repainting issues or platform quirks. You can track historical values and use table-based monitors to watch real-time variables, isolating logic discrepancies across single indicators and complex strategies.

Can I inspect Pine Script variables on the chart without using print statements?

You can inspect Pine Script variables directly on the chart using label-based debugging. This method attaches value inspections to specific bars, bypassing console limitations and allowing immediate visual tracing of script behavior.

Does this debugging approach work for both indicators and complex strategies?

This debugging approach works across single indicators and complete strategies in Pine Script. It handles both real-time and historical backtest contexts, providing diagnostic utilities for runtime errors and performance issues.

What is the best way to monitor Pine Script performance bottlenecks?

The best way to monitor Pine Script performance bottlenecks is using table-based real-time monitors and historical value tracking. These utilities help identify slow calculations and platform quirks affecting script execution.