feature-f6-volume-spike-cancel

Cancels pending trading orders when the 1-second traded volume exceeds a threshold and blocks re-entry for the day.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/13g7895123/littile-bao --skill feature-f6-volume-spike-cancel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-f6-volume-spike-cancel
Source: https://github.com/13g7895123/littile-bao/tree/main/.github/skills/feature-f6-volume-spike-cancel
Command: npx skills add https://github.com/13g7895123/littile-bao --skill feature-f6-volume-spike-cancel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When market activity suddenly spikes, pending orders can get stuck and repeatedly fail to execute efficiently, causing wasted risk exposure and unnecessary order churn.

Core Features & Use Cases

  • Pending order spike cancellation: Monitors pending orders and cancels them when the most recent 1-second traded volume exceeds a configurable threshold.
  • Same-day entry blocking: After cancellation, marks the symbol for “entry blocked” to prevent immediate re-entries and reduce thrashing.
  • Configurable behavior: Uses f6_enabled to turn the feature on/off and volume_spike_cancel_threshold to tune sensitivity; intended for tuning and control alongside related logic (e.g., F4/F5 exits).

Quick Start

Enable F6 and set volume_spike_cancel_threshold to match your desired sensitivity so that any pending order with last_1s_vol above the threshold gets canceled and then blocked for the day.

Frequently Asked Questions about feature-f6-volume-spike-cancel

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

FAQPage Schema
How do I cancel pending trading orders during a volume spike?

Cancel pending trading orders during a volume spike by enabling the f6 feature, which monitors the last 1-second traded volume and cancels any pending order that exceeds your configured volume_spike_cancel_threshold. The cancellation occurs during engine tick evaluation before position-based exit logic is applied.

Why do my pending orders get stuck and churn during sudden market activity spikes?

Pending orders get stuck during market activity spikes because they repeatedly fail to execute efficiently, causing wasted risk exposure. A volume spike cancellation feature addresses this by canceling these pending orders and setting an entry blocked state to prevent same-day re-entries and reduce thrashing.

How do I configure order cancellation sensitivity for 1s volume spikes?

Configure order cancellation sensitivity by setting the volume_spike_cancel_threshold parameter to your desired volume level. Toggle the f6_enabled parameter to turn the feature on or off, allowing you to tune how aggressively pending orders are canceled when the last 1s traded volume exceeds the threshold.

Does canceling a pending order on a volume spike block re-entry for the rest of the day?

Yes, canceling a pending order on a volume spike blocks re-entry for the rest of the day. After invoking the order cancellation, the system sets state.entry_blocked to True, which prevents immediate same-day re-entries and reduces order thrashing for that specific symbol.

When does the volume spike cancellation logic execute during the backtesting engine tick?

The volume spike cancellation logic executes during engine tick evaluation while an order is still pending and not yet filled. It runs specifically before any position-based exit logic is evaluated, ensuring pending orders are canceled before downstream exit rules are applied.