- Home
- Skills
- Testing & Debugging
- Feature Flag Preflight
Feature Flag Preflight
Validate feature flag targeting, simulate rollout blast radius, and generate executable regression tests.
$5.80
Works with the AI Agents you already use
Feature Flag Preflight
Example session with this skill installed
Run a preflight check on my proposed ruleset in config/flags/new_feature.json. Compare it against the current production-flags.json and generate regression tests.
- Read your context and instructions
- Compiled the feature flag preflight
Feature Flag Preflight — Example Audit Report
Release recommendation: BLOCK
The preflight analysis identified configuration problems that should be resolved before the proposed feature flags are released.
1. Configuration Validation
| Check | Status | Finding |
|---|---|---|
| Targeting rules | WARNING | A catch-all rule may shadow a lower-priority rule |
| Distribution weights | BLOCK | One rollout rule allocates only 75% instead of 100% |
| Default variations | PASS | No missing defaults identified in this example |
| Release readiness | BLOCK | Configuration errors require attention |
2. Rollout Safety
Feature Flag Preflight supports deterministic MurmurHash3 bucketing, rollout simulation, and comparison with a baseline configuration.
Where enough representative contexts are available, the report can show assignment transitions, statistical checks, and potential cohort churn.
Checks with insufficient evidence are explicitly marked INCONCLUSIVE or SKIPPED.
3. Regression Tests
The skill can generate executable pytest regression tests covering targeting behavior, fallback values, individual overrides, and stable user assignment.
Tests can be executed locally to help verify configuration changes before deployment.
4. Recommended Actions
- Correct the invalid distribution so that weights total 100%.
- Review targeting rule priorities and remove unintended shadowing.
- Run Feature Flag Preflight again against the corrected configuration.
- Review the updated report before proceeding to staging.
Deliverables
preflight-report.md— Human-readable audit reportpreflight-report.json— Machine-readable findings- Generated pytest regression tests
Next step: Fix the reported configuration issues and rerun the preflight checks.
Illustrative demo based on the types of issues detected in the included sample configurations. Actual findings depend on the supplied rulesets and contexts.
Connects securely to your tools. The creator never sees your data.
About this skill
Feature Flag Preflight helps developers detect feature flag configuration mistakes before deployment. It validates targeting rules, simulates percentage rollouts, identifies potential release risks, and generates executable regression tests. Run these checks locally without connecting to a production server.
What it does
- Audit configurations by scanning rulesets for shadowed rules, invalid operators, and distribution sum errors.
- Simulate rollouts using Monte Carlo simulations to quantify blast radius and verify MurmurHash3 bucketing.
- Synthesize regression tests by generating executable pytest suites that validate fallback behavior and overrides.
- Analyze comparative impact to detect user assignment churn between current and candidate configurations.
- Verify monotonicity to ensure that increasing a rollout percentage doesn't unexpectedly revoke access for existing users.
How it works
- Identify assets by pointing the agent to your
ruleset.jsonand optional baseline or user context files. - Execute preflight using the
scripts.preflightcommand with flags for test generation or strict CI enforcement. - Review recommendations based on the automated
PASS,REVIEW, orBLOCKdecision badges and exit codes. - Inspect artifacts including the Markdown executive summary and machine-readable JSON audit reports.
Frameworks & tools
This tool works with JSON-based feature flag configurations, pytest for regression execution, and standard Python environments. It is designed for OpenFeature providers, FlagOps exports, and custom ruleset architectures.
Why this beats prompting it yourself
Generic prompts often miss the nuances of MurmurHash3 bucketing and statistical significance in distribution weights. This skill uses specific Monte Carlo simulations and 29 pre-defined safety checks to find edge cases like hash collisions and shadowed rules that LLMs typically overlook in raw text analysis.
Use cases
- Pull Request audits to catch targeting logic errors before they reach the main branch.
- Canary planning to calculate the exact blast radius when moving from 10% to 25%.
- Anomalous behavior triage to investigate why specific users are hitting fallback variations.
- Automated QA for generating test fixtures that protect critical flag overrides.
Known limitations
Does not replace end-to-end application business logic testing. Statistical verification requires at least 50 unique contexts to be conclusive. Direct code string interpolation is not supported.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Testing & Debugging.
Requires at least 50 unique contexts for statistical significance. Does not test application business logic or live service endpoints. No secret handling or network I/O supported.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 23 days ago
- Software
Python
Permissions
File Scopes
Requires terminal access to run local Python validation and pytest tests, read access to user-selected JSON configuration files, and write access to generate reports and regression tests. No network access, browser access, API keys, or external accounts are required.