batch-impact-regression

Analyze C# and SQL Server batch changes with deterministic combination regression comparison.

4|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/synthaicode/XRefKit --skill batch-impact-regression-synthaicode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: batch-impact-regression
Source: https://github.com/synthaicode/XRefKit/tree/main/packages/xrefkit-skills-batch-regression/src/xrefkit_skills_batch_regression/skill_assets/mcp_skill
Command: npx skills add https://github.com/synthaicode/XRefKit --skill batch-impact-regression-synthaicode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? When a requirement changes an existing C# batch backed by SQL Server stored procedures, teams struggle to predict impact across huge input combinations, trace execution paths across both layers, and prove that new behavior matches expectations without running unsafe tests against production. ## Core Features & Use Cases - Deterministic Combination Analysis: Generate Cartesian candidate sets, apply declarative constraints, and build strength-2 pairwise orthogonal tables without sending the full candidate space to the model. - Old/New Result Comparison: Normalize and classify adapter-produced JSON records into baseline_match, planned_difference, unexplained_difference, business_invalid, system_error, uncertain, and not_executed categories. - Source Decision-Table Extraction: Scan .cs and .sql files to extract if/when/case conditions, factors, and literal values with file-and-line evidence, keeping unresolved expressions as explicit uncertainties. - Use Case: A requirement changes a nightly batch's parameter handling. Use this Skill to trace the C#-to-SP execution path, generate a constrained candidate set, compare old and new isolated-database runs, and produce a reduced regression set with human-gated release decisions. ## Quick Start Ask the AI to use the batch-impact-regression skill to analyze your C# batch and SQL Server stored procedure change and produce a combination regression report from your configuration file.

Frequently Asked Questions about batch-impact-regression

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

FAQPage Schema
How do I regression test a C# batch that calls SQL Server stored procedures?▼

Define combination dimensions and constraints in a JSON config, run old and new versions through an isolated adapter that emits the JSON record contract, then run the batch_regression.py report command to classify differences and select a reduced regression set.

How do I extract decision tables from C# and SQL source code?▼

Run the extract-tables command on the source root to scan .cs and .sql files for if, when, and case conditions. It emits a decision table, factor values with file-and-line evidence, a pairwise orthogonal table, and unresolved expressions listed as uncertainties.

Can this run regression tests against a production database?▼

No. The Skill explicitly forbids executing against production and requires an isolated adapter targeting a cloned, snapshot, or disposable database. Side effects must be verified with before/after row counts and human-approved rollback or restore.

What happens with dynamic SQL or unresolved stored procedure names?▼

Dynamic SQL and dynamically resolved SP names are recorded as uncertain rather than guessed. The affected paths and candidate counts stay flagged until runtime evidence closes them, and unresolved items are escalated for human judgment.

What are the limitations of the source code scanner?▼

The scanner is a syntax-based extractor, not a C# or T-SQL compiler, so reflection, generated code, macros, and complex multi-line expressions may remain unresolved. Extracted conditions are evidence for review and are never promoted to business rules automatically.