stock-backtest

To backtest stock patterns, you can export K-line data from a PostgreSQL server to local CSV or JSON files. This allows you to run pattern backtesting and validate your trading strategies against real historical data.

Yes, you need SSH access to export stock data for local backtesting. The process requires SSH-based remote export from a Dockerized PostgreSQL environment to securely retrieve and store your historical K-line data locally.

The best way to run batch backtests across multiple stocks is to export the required data locally and use a configurable detection strategy. This skill supports batch-style processing to generate comparative backtesting reports.

Yes, you can use PostgreSQL K-line data to generate backtest reports locally. After exporting the data via base64-encoded commands, the skill performs local backtesting and outputs a Markdown report for your analysis.

SSH remote export works by securely transferring base64-encoded commands to a Docker container containing PostgreSQL. This mechanism safely executes queries on the server to extract K-line data without manual data gathering.

A limitation is that all exported stock data must be stored locally under the data/backtest directory as CSV or JSON. This ensures reproducible backtests but requires adequate local storage capacity for large historical datasets.