verify-before-done

To verify code changes before turn completion, use an exit gate that checks for saved files and passing verification commands. This ensures development workflows require written files and successful tests or typechecks before final replies are allowed.

Enforcing coding standards at turn completion involves acting as an exit gate that validates file management and verification commands. This mechanism guarantees code changes are accompanied by documentation and passing tests before proceeding.

Automate file verification and test checks by validating that changes were saved using file editing tools and that required verification commands have run successfully. This confirms code changes meet completion criteria.

Yes, you can block final replies by implementing a verification gate that only allows completion after checks pass. This ensures required verification commands like tests and typechecks are successfully run.

Turn completion without verification happens when no exit gate enforces coding standards. Adding a verification step ensures code changes are accompanied by written files and passing verification commands before completion.

The verify-before-done skill works with file management and testing workflows by checking if changes were saved with file editing tools and ensuring required verification commands have been run successfully before allowing completion.