double-check

What This Skill Does

The Double-Check Skill for OpenClaw is an essential reliability utility designed to automate the verification process after any file-based modification. By default, this skill ensures that all changes—whether it is adding a new feature, refactoring existing code, or deleting deprecated functionality—are subjected to a rigorous dual-validation process. The core mechanism requires that after any modification, the system performs the same verification command twice consecutively. This minimizes the risk of non-deterministic errors, silent failures, or environment-specific bugs slipping into the codebase. When this skill is active, you will see a "✅✅" prefix in the AI's response, signaling that the safety protocol is enabled and protecting your project integrity.

Installation

To install this skill, run the following command in your terminal or via the OpenClaw command interface: clawhub install openclaw/skills/skills/belugarex/double-check

Use Cases

This skill is highly versatile and acts as a safeguard in the following scenarios:

• Refactoring: Validating that complex code changes do not break existing logic by running test suites multiple times.
• Feature Removal: Ensuring that when you delete legacy features, all associated imports, configurations, and dependencies are successfully cleaned up without causing runtime crashes.
• Dependency Updates: Confirming that new package versions are compatible with your current build environment through repeated compilation checks.
• Configuration Tuning: Verifying that environment variable or configuration file changes do not prevent your application from starting correctly.

Example Prompts

1. "Please remove the legacy authentication module from the user controller and double-check that the system remains stable."
2. "Refactor the database connection pool in db.py to use a singleton pattern, ensuring all unit tests pass reliably."
3. "Update the package.json to include the latest security patches and confirm the build process works successfully twice."

Tips & Limitations

• Consistency is Key: The skill relies on you having a defined validation command. If your project lacks an automated test suite, ensure you have a reliable "start" or "check" command to serve as your verification gate.
• Performance Overhead: Because this skill runs validations twice to ensure consistency, it may increase total processing time for large projects or complex build pipelines.
• Independence: While the commands used are identical, you should ensure your environment or build tools do not cache artifacts between these two runs, or use flags like --no-cache to ensure true independence.