repainting fake signal inspector

The problem

TradingView backtests often show impossible returns due to hidden coding errors. Pine Script strategies frequently suffer from repainting and lookahead bias, where the script "sees" future prices to trigger perfect entries that can never happen in live trading.

What it does

• Identifies repainting risks in request.security calls and indicator calculations.
• Detects lookahead bias where stops or targets use current bar data before it exists.
• Audits strategy() parameters for unrealistic slippage, commission, and fill assumptions.
• Flags duplicate signal logic that artificially inflates trade counts or equity curves.
• Provides concrete Pine Script code fixes for every high-severity finding.

Frameworks & tools

TradingView Pine Script (v4 and v5).

Why this beats prompting it yourself

Generic LLMs often miss subtle execution nuances like process_orders_on_close interactions or barstate persistence. This skill uses a specialized audit workflow to trace the order lifecycle bar-by-bar, catching logic traps that pass standard syntax checks.

Use cases

• Verifying a purchased or open-source Pine Script strategy before risking capital.
• Debugging "too good to be true" backtest results that disappear in forward testing.
• Hardening entry and exit logic to ensure signals confirm only on closed bars.
• Adding realistic execution constraints like slippage and commissions to existing scripts.

Known limitations

Cannot execute the code to see visual repainting; relies entirely on static analysis of the provided script logic.