Agent skill

Interval Guided Regression Test Update

by ArabelaTso in ArabelaTso/Skills-4-SE

Automatically updates regression tests based on interval analysis to maintain coverage of key program intervals.

Apache-2.0Auto-check passedTesting & QA

Install Interval Guided Regression Test Update

skills CLI
$ npx skills add ArabelaTso/Skills-4-SE --skill interval-guided-regression-test-update -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ArabelaTso/Skills-4-SE interval-guided-regression-test-update --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/interval-guided-regression-test-update .claude/skills/interval-guided-regression-test-update && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
interval-guided-regression-test-update
GitHub stars
253
Token cost
~2.7k tokens
SKILL.md length
827 words
Files
3 (incl. references)
Skills in repo
170
Repo updated
First seen
Licence
Apache-2.0

At a glance

Automatically updates regression tests based on interval analysis to maintain coverage of key program intervals.

  • Works in 6 steps: Analyze Existing Tests → Extract Interval Information → Identify Coverage Gaps → …
  • Code changes affect value ranges
  • SKILL.md covers Core Concept, Workflow, Quick Start Examples and Update Strategies, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Interval Guided Regression Test Update is an agent skill from ArabelaTso/Skills-4-SE. Automatically updates regression tests based on interval analysis to maintain coverage of key program intervals. Use when code changes affect value ranges, conditionals, or control flow, and existing tests need updating to maintain interval coverage. Analyzes interval information from updated code, identifies coverage gaps, adjusts test inputs and assertions, removes redundant tests, and generates new tests for uncovered intervals. Supports Python, Java, JavaScript, and C/C++ with various test frameworks (pytest…

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/interval-analysis.md` and `references/test-update-strategies.md`).

It sits in Testing & QA, covering Unit testing and Test coverage. It works with Jest, JUnit, pytest and C++. The repository describes itself as: A curated list of 180+ useful Claude Skills for Software Engineering and resources for customizing AI for SE workflows. The licence is Apache-2.0.

When your agent uses it

  • Code changes affect value ranges
  • Existing tests need updating to maintain interval coverage

Example prompts

  • “/interval-guided-regression-test-update”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Analyze Existing Tests
  2. Extract Interval Information
  3. Identify Coverage Gaps
  4. Update Tests
  5. Validate Updated Tests
  6. Generate Coverage Report

What it can do on your machine

Read from SKILL.md and the folder at commit 4f38503. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are python).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Interval Guided Regression Test Update loads about 2.7k tokens when it runs, and up to ~7k if it reads all its reference files. Until then it costs about 146 tokens; SKILL.md has 827 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~146
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ArabelaTso/Skills-4-SE at commit 4f38503, republished under its Apache-2.0 licence (© ArabelaTso). 827 words, ~2,677 tokens.

Download SKILL.mdSave it as .claude/skills/interval-guided-regression-test-update/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
interval-guided-regression-test-update
description
Automatically updates regression tests based on interval analysis to maintain coverage of key program intervals. Use when code changes affect value ranges, conditionals, or control flow, and existing tests need updating to maintain interval coverage. Analyzes interval information from updated code, identifies coverage gaps, adjusts test inputs and assertions, removes redundant tests, and generates new tests for uncovered intervals. Supports Python, Java, JavaScript, and C/C++ with various test frameworks (pytest, JUnit, Jest, Google Test).

Interval-Guided Regression Test Update

Automatically update regression tests to maintain interval coverage when program code changes.

Core Concept

Intervals represent ranges of values that variables can take during execution. When code changes, intervals may be added, removed, or modified. This skill ensures regression tests continue to cover all important intervals.

Example:

python
# Old code
def process(x):
    if x < 10:
        return x * 2
    else:
        return x + 10

# Intervals: [0, 10), [10, ∞)

# New code (added negative handling)
def process(x):
    if x < 0:
        return -x
    elif x < 10:
        return x * 2
    else:
        return x + 10

# Intervals: (-∞, 0), [0, 10), [10, ∞)
# Need to add test for new interval: x < 0

Workflow

1. Analyze Existing Tests

Parse the current regression test suite:

  • Identify test inputs
  • Determine which intervals each test covers
  • Calculate current interval coverage
python
# Example test analysis
test_process_small: input=5, covers [0, 10)
test_process_large: input=15, covers [10, ∞)
# Coverage: 2/2 intervals = 100%
2. Extract Interval Information

Obtain interval information from the updated program:

From static analysis:

  • Parse conditionals (if, switch, etc.)
  • Extract comparison operators
  • Derive interval constraints

From profiling:

  • Run existing tests
  • Track observed value ranges
  • Identify intervals exercised

From symbolic execution:

  • Execute with symbolic values
  • Collect path constraints
  • Derive interval constraints

See references/interval-analysis.md for detailed extraction methods.

3. Identify Coverage Gaps

Compare current coverage with new intervals:

python
old_intervals = {[0, 10), [10, ∞)}
new_intervals = {(-∞, 0), [0, 10), [10, ∞)}

added_intervals = {(-∞, 0)}  # Need new test
removed_intervals = {}
modified_intervals = {}
4. Update Tests

Apply appropriate update strategies:

Add tests for new intervals:

python
# New test for (-∞, 0)
def test_process_negative():
    assert process(-5) == 5

Adjust inputs for modified intervals:

python
# If boundary changed from x < 10 to x < 20
# Old: test_process_large with input=15
# New: test_process_large with input=25

Update assertions for changed behavior:

python
# If logic changed
# Old: assert process(5) == 10
# New: assert process(5) == 15

Remove redundant tests:

python
# If intervals merged, remove duplicate coverage

See references/test-update-strategies.md for detailed strategies.

5. Validate Updated Tests

Run the updated test suite:

  • Execute all tests
  • Verify all pass
  • Check interval coverage
  • Identify any remaining gaps
6. Generate Coverage Report

Provide comprehensive summary:

  • Before/after interval coverage
  • Tests added, modified, removed
  • Validation results
  • Remaining gaps (if any)

Quick Start Examples

Example 1: New Interval Added

Scenario: Function adds handling for negative numbers

Original code:

python
def abs_double(x):
    if x < 10:
        return x * 2
    else:
        return x + 10

Original tests:

python
def test_small():
    assert abs_double(5) == 10

def test_large():
    assert abs_double(15) == 25

Updated code:

python
def abs_double(x):
    if x < 0:
        return -x * 2
    elif x < 10:
        return x * 2
    else:
        return x + 10

Updated tests:

python
def test_negative():  # NEW
    assert abs_double(-5) == 10

def test_small():
    assert abs_double(5) == 10

def test_large():
    assert abs_double(15) == 25

Summary:

  • Added interval: (-∞, 0)
  • Added test: test_negative
  • Coverage: 2/2 → 3/3 (100%)
Example 2: Interval Boundary Changed

Scenario: Threshold value modified

Original code:

python
def categorize(score):
    if score < 60:
        return "fail"
    else:
        return "pass"

Original tests:

python
def test_fail():
    assert categorize(50) == "fail"

def test_pass():
    assert categorize(70) == "pass"

Updated code:

python
def categorize(score):
    if score < 50:  # Changed from 60
        return "fail"
    else:
        return "pass"

Updated tests:

python
def test_fail():
    assert categorize(40) == "fail"  # Changed input from 50

def test_pass():
    assert categorize(60) == "pass"  # Changed input from 70

Summary:

  • Modified interval: [0, 60) → [0, 50)
  • Modified interval: [60, ∞) → [50, ∞)
  • Updated 2 test inputs
  • Coverage: 2/2 → 2/2 (100%)
Example 3: Intervals Merged

Scenario: Simplified logic combines cases

Original code:

python
def classify(x):
    if x < 0:
        return "negative"
    elif x == 0:
        return "zero"
    else:
        return "positive"

Original tests:

python
def test_negative():
    assert classify(-5) == "negative"

def test_zero():
    assert classify(0) == "zero"

def test_positive():
    assert classify(5) == "positive"

Updated code:

python
def classify(x):
    if x <= 0:
        return "non-positive"
    else:
        return "positive"

Updated tests:

python
def test_non_positive():  # Merged
    assert classify(-5) == "non-positive"
    assert classify(0) == "non-positive"

def test_positive():
    assert classify(5) == "positive"

Summary:

  • Merged intervals: (-∞, 0) and {0} → (-∞, 0]
  • Removed test: test_zero (redundant)
  • Updated test: test_negative → test_non_positive
  • Coverage: 3/3 → 2/2 (100%)

Update Strategies

Strategy 1: Input Adjustment

Modify test inputs to cover new or changed intervals.

When to use:

  • New interval added
  • Interval boundary changed
  • Need to cover previously uncovered interval

How:

  1. Identify target interval
  2. Select representative value from interval
  3. Update test input
  4. Verify test still valid
Strategy 2: Assertion Update

Modify expected values when behavior changes.

When to use:

  • Logic changed within interval
  • Return value modified
  • Side effects changed

How:

  1. Execute test with new code
  2. Observe actual output
  3. Verify output is correct
  4. Update assertion
Strategy 3: Test Removal

Remove redundant or obsolete tests.

When to use:

  • Intervals merged
  • Multiple tests cover same interval
  • Interval no longer exists

How:

  1. Identify redundant tests
  2. Keep most representative test
  3. Remove others
  4. Verify coverage maintained
Strategy 4: Test Generation

Create new tests for uncovered intervals.

When to use:

  • New interval added
  • Coverage gap identified
  • No existing test covers interval

How:

  1. Identify uncovered interval
  2. Generate representative input
  3. Determine expected output
  4. Create new test

Coverage Analysis

Computing Coverage
Interval Coverage = (Covered Intervals) / (Total Intervals) × 100%

Example:

Total intervals: 4
Covered by tests: 3
Coverage: 75%
Show full SKILL.md (330 more words)Show less
Coverage Report Format
Interval Coverage Report
========================

Before Update:
- Total intervals: 2
- Covered intervals: 2
- Coverage: 100%

After Update:
- Total intervals: 3
- Covered intervals: 3
- Coverage: 100%

Changes:
- Added intervals: 1
- Removed intervals: 0
- Modified intervals: 0

Test Changes:
- Added tests: 1
- Modified tests: 0
- Removed tests: 0

Best Practices

Minimize Changes
  • Only update tests affected by code changes
  • Preserve tests that still provide value
  • Avoid unnecessary rewrites
Maintain Test Quality
  • Use descriptive test names
  • Keep tests simple and focused
  • Document why tests were updated
Validate Thoroughly
  • Run all tests after updates
  • Check coverage metrics
  • Verify no regressions
Document Changes
  • Record what changed and why
  • Note any manual adjustments
  • Track coverage improvements

Common Scenarios

Scenario 1: Refactoring with Logic Change

Problem: Code refactored, some logic changed

Solution:

  1. Extract intervals from new code
  2. Compare with old intervals
  3. Update tests for changed intervals
  4. Verify all tests pass
Scenario 2: Feature Addition

Problem: New feature adds new code paths

Solution:

  1. Identify new intervals
  2. Generate tests for new intervals
  3. Ensure existing tests still valid
  4. Verify complete coverage
Scenario 3: Bug Fix

Problem: Bug fix changes behavior in specific interval

Solution:

  1. Identify affected interval
  2. Update test for that interval
  3. Add regression test if needed
  4. Verify fix doesn't break other intervals

Troubleshooting

Tests Fail After Update

Check:

  • Assertions match new behavior
  • Inputs are valid for new code
  • Expected values are correct

Solution:

  • Review code changes carefully
  • Execute tests manually
  • Update assertions as needed
Coverage Decreased

Check:

  • New intervals added
  • Tests removed incorrectly
  • Intervals not properly identified

Solution:

  • Identify uncovered intervals
  • Generate missing tests
  • Verify interval extraction
Redundant Tests

Check:

  • Multiple tests cover same interval
  • Intervals merged in new code

Solution:

  • Identify redundant tests
  • Keep most representative
  • Remove duplicates

References

  • interval-analysis.md: Comprehensive guide to interval concepts, extraction methods, and coverage analysis
  • test-update-strategies.md: Detailed strategies for updating tests including input adjustment, assertion updates, and test generation

Tips

  • Start with coverage analysis: Understand current coverage before making changes
  • Use interval extraction tools: Leverage static analysis or profiling tools
  • Update incrementally: Make one change at a time and validate
  • Preserve test intent: Keep the purpose of each test clear
  • Document assumptions: Note any assumptions about intervals
  • Validate coverage: Always verify coverage after updates

© ArabelaTso, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/interval-guided-regression-test-update of ArabelaTso/Skills-4-SE.

  • SKILL.md
  • references/interval-analysis.md
  • references/test-update-strategies.md

Open the folder on GitHubat commit 4f38503

Compare with similar skills

Interval Guided Regression Test Update next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Interval Guided Regression Test Update compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Interval Guided Regression Test Update this skillArabelaTso/Skills-4-SE253—~2.7kAutomated safety check: PassApache-2.0
Test Smell Detectionmicrosoft/testfx1k—~5.3kAutomated safety check: PassMIT
TDD GuideLeoYeAI/openclaw-master-skills2.2k—~1.4kAutomated safety check: PassMIT
TDD Guidealirezarezvani/claude-skills28k—~3.4kAutomated safety check: PassMIT
Python Testing Patternsjh941213/my-cc-harness12617 repos~5.4kAutomated safety check: PassNone
Test Analysis Extensionsmicrosoft/testfx1k2 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Test Smell Detection

    microsoft/testfx

    Official

    Deep-dive audit using the full testsmells.org 19-smell academic catalog for tests in any language.

    1k GitHub stars~5.3k tokensUpdated today
    Testing & QAAuto-check passed
  • TDD Guide

    LeoYeAI/openclaw-master-skills

    Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and…

    2.2k GitHub stars~1.4k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed
  • TDD Guide

    alirezarezvani/claude-skills

    Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and…

    28k GitHub stars~3.4k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • Python Testing Patterns

    jh941213/my-cc-harness

    Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development.

    126 GitHub starsUsed in 17 repos~5.4k tokens
    Testing & QAAuto-check passed
  • Test Analysis Extensions

    microsoft/testfx

    Official

    Provides file paths to language-specific reference files for the test ANALYSIS skills (assertion-quality, test-anti-patterns, test-gap-analysis, test-smell-detection, test-tagging).

    1k GitHub starsUsed in 2 repos~1.1k tokens
    Testing & QAAuto-check passed
  • Assertion Quality

    microsoft/testfx

    Official

    Analyzes the variety and depth of assertions across test suites in any language.

    1k GitHub stars~4.1k tokensUpdated today
    Testing & QAAuto-check passed

More from ArabelaTso/Skills-4-SE

All 170 skills in this repo
  • Framework Migration Assistant

    ArabelaTso/Skills-4-SE

    Automatically migrate Python web applications between frameworks (Flask → FastAPI, Django → FastAPI).

    253 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Metamorphic Test Generator

    ArabelaTso/Skills-4-SE

    Generate test cases using metamorphic testing by applying transformations based on metamorphic properties.

    253 GitHub stars~798 tokensUpdated 1 mo ago
    Auto-check passed
  • Reproduction Trace Instrumenter

    ArabelaTso/Skills-4-SE

    Instruments programs to capture execution traces specifically for reproducing reported bugs, enabling consistent replay and diagnosis of failures.

    253 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Spring Mvc To Boot Migrator

    ArabelaTso/Skills-4-SE

    Automatically migrate Spring MVC applications to Spring Boot.

    253 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed
  • State Snapshot Instrumenter

    ArabelaTso/Skills-4-SE

    Instrument programs (Python, C/C++, Java) to capture snapshots of key program states at runtime, including variables, memory, and call stacks.

    253 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Interval Guided Regression Test Update

What does Interval Guided Regression Test Update do?

Automatically updates regression tests based on interval analysis to maintain coverage of key program intervals. Interval Guided Regression Test Update is an agent skill from ArabelaTso/Skills-4-SE. Automatically updates regression tests based on interval analysis to maintain coverage of key program intervals.

When should I use Interval Guided Regression Test Update?

Interval Guided Regression Test Update fits situations like: code changes affect value ranges; existing tests need updating to maintain interval coverage.

How do I install Interval Guided Regression Test Update in Claude Code?

Run `npx skills add ArabelaTso/Skills-4-SE --skill interval-guided-regression-test-update -a claude-code`. Or copy the skill folder (skills/interval-guided-regression-test-update in ArabelaTso/Skills-4-SE) into .claude/skills/interval-guided-regression-test-update in your project. Claude Code loads it when a task matches its description.

How do I install Interval Guided Regression Test Update in Codex?

Run `npx skills add ArabelaTso/Skills-4-SE --skill interval-guided-regression-test-update -a codex`. Or copy the skill folder (skills/interval-guided-regression-test-update in ArabelaTso/Skills-4-SE) into .agents/skills/interval-guided-regression-test-update in your project. Codex loads it when a task matches its description.

Can I use Interval Guided Regression Test Update in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ArabelaTso/Skills-4-SE --skill interval-guided-regression-test-update -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/interval-guided-regression-test-update, .gemini/skills/interval-guided-regression-test-update, .github/skills/interval-guided-regression-test-update and .opencode/skills/interval-guided-regression-test-update in your project.

What does Interval Guided Regression Test Update need to run?

SKILL.md names no scripts, command-line tools or credentials: Interval Guided Regression Test Update is instructions for the agent only. Our summary lists: Python 3.

Does Interval Guided Regression Test Update access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Interval Guided Regression Test Update safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Interval Guided Regression Test Update use?

Interval Guided Regression Test Update is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Interval Guided Regression Test Update use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.3k tokens, read only when the agent opens those files.

What are the alternatives to Interval Guided Regression Test Update?

Skills that share tags, products or a category with Interval Guided Regression Test Update: Test Smell Detection (microsoft/testfx, 1k stars), TDD Guide (LeoYeAI/openclaw-master-skills, 2.2k stars), TDD Guide (alirezarezvani/claude-skills, 28k stars) and Python Testing Patterns (jh941213/my-cc-harness, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Interval Guided Regression Test Update?

ArabelaTso (a GitHub user) maintains it in ArabelaTso/Skills-4-SE, which has 253 GitHub stars. The repository holds 170 skills in this directory. The repository was last updated on August 21, 2026.

Source: ArabelaTso/Skills-4-SE on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.