Quality Verification

输出质量保障与验证。编辑后检查、提交前测试、session 指标测量。不适用于工具重试（用 tool-governance）或 agent 提前停止（用 execution-loop）。参见 tool-governance（错误追踪）。

What to consider before installing: - This skill runs local linters and project test commands. test-before-commit will execute repository test runners (npm/pytest/cargo/go test/make), which can run arbitrary code from the repo — avoid enabling this on repositories you don't trust. TEST_BEFORE_COMMIT is disabled by default; only set TEST_BEFORE_COMMIT=1 if you understand and accept this behavior. - The skill writes session state under $HOME/.openclaw/shared-context/sessions (creates/updates bracket.json and session dirs). Review and control permissions for that directory if sensitive. - Documentation mentions runtime profile controls (HARNESS_PROFILE, HARNESS_DISABLED_HOOKS) and a session-cleanup script, but those controls are not consistently enforced across all shipped scripts; expect some manual configuration or code review to align behavior with your security posture. - Recommended actions: review the three provided scripts (post-edit-check.sh, test-before-commit.sh, bracket-hook.sh), run them in a safe sandbox or test repo first, and keep TEST_BEFORE_COMMIT disabled until you confirm tests/lint commands are safe. If you open untrusted workspaces, disable Bash hooks or enforce a workspace-trust policy so hooks cannot execute repository-provided test code.

Type: OpenClaw Skill Name: quality-verification Version: 2.4.0 The quality-verification skill bundle provides legitimate development workflow enhancements, including automated linting (post-edit-check.sh), pre-commit test validation (test-before-commit.sh), and session performance tracking (bracket-hook.sh). The scripts use standard development tools like ruff, tsc, and pytest, and their behavior is strictly aligned with the documented purpose of ensuring code quality and session monitoring without any signs of data exfiltration, unauthorized persistence, or malicious prompt injection.