fix-local-tests

Fix failing rshell tests by aligning implementation with bash behavior.

31|3|Updated Mar 8, 2026

Search Tags:#testing #debugging #compatibility #bash #regression #shell

Ready to run

npx skills add https://github.com/DataDog/rshell --skill fix-local-tests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix-local-tests
Source: https://github.com/DataDog/rshell/tree/main/.claude/skills/fix-local-tests
Command: npx skills add https://github.com/DataDog/rshell --skill fix-local-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses discrepancies between rshell's test suite and the expected behavior of bash, ensuring greater compatibility and correctness.

Core Features & Use Cases

Failure Reproduction: Captures and analyzes test failures by running relevant test suites.
Behavior Verification: Determines the correct bash behavior for failing scenarios using comparison tests or Docker.
Root Cause Analysis: Classifies failures as implementation bugs, incorrect test expectations, or intentional divergences.
Prioritized Fixing: Guides the user to fix implementation bugs first, then test expectations, and finally fuzz failures.
Use Case: When a test in the rshell project fails, use this Skill to systematically debug and fix the issue by comparing rshell's output to bash's expected output.

Quick Start

Run the fix-local-tests skill with the argument 'TestName' to reproduce and fix a specific failing test.

Frequently Asked Questions about fix-local-tests

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

FAQPage Schema

How do I fix failing shell tests when my implementation doesn't match bash behavior?▼

To fix failing shell tests, you need to analyze the test failures, determine the correct bash behavior, and classify whether the discrepancy is an implementation bug, an incorrect test expectation, or an intentional divergence before applying fixes.

What is the best way to debug an rshell test failure against expected bash output?▼

Debugging an rshell test failure involves reproducing the error, running comparison tests to verify expected bash behavior, and then systematically guiding fixes prioritized as implementation bugs, test expectations, and fuzz failures.

How do I classify shell test discrepancies to know if my code or my test is wrong?▼

Classifying shell test discrepancies requires comparing your shell's output to bash's expected behavior to determine if the failure stems from an implementation bug, an incorrect test expectation, or an intentional divergence in the project.

Why do my local shell regression tests fail even when the implementation seems correct?▼

Local shell regression tests fail when there are discrepancies between your shell implementation and expected bash behavior, requiring you to run comparison tests to verify the correct behavior and classify the root cause before fixing.

Can I use Docker to verify bash behavior for failing shell compatibility tests?▼

Yes, you can use Docker or bash comparison tests to verify the correct bash behavior for failing scenarios, ensuring your shell implementation fixes align with the expected compatibility standards before running the full test suite.

What should I do after fixing a shell implementation bug to prevent regression?▼

After fixing a shell implementation bug, you should verify all fixes against the full test suite and bash comparison tests to ensure the changes align with bash behavior and prevent future regressions.