Quality Gates

Quality checkpoints at every development stage — pre-commit through post-deploy — with configuration examples, threshold tables, bypass protocols, and CI/CD integration. Use when setting up quality automation, configuring CI pipelines, establishing coverage thresholds, or defining deployment requirements.

This is a documentation-only skill that provides recipes for pre-commit hooks and CI quality gates — it appears coherent and safe as-is. Before you adopt its recommendations: review any hook scripts and GitHub Actions it suggests (pin action versions, prefer official authors), verify third-party tools (gitleaks, trivy, trufflehog, etc.) come from trusted sources, and apply least-privilege to any CI or deploy tokens you create. Also be aware that some recommended gates (e.g., 100% E2E coverage or strict deploy automation) may be unrealistic for your project; adapt thresholds accordingly. Because the skill does not request credentials, installing it won’t expose secrets by itself, but implementing its CI/deploy recipes will require you to supply credentials to your CI/CD system — handle those secrets per your security policies.

Type: OpenClaw Skill Name: quality-gates Version: 0.1.0 The skill bundle provides comprehensive documentation and configuration examples for implementing quality gates in software development. The `SKILL.md` file contains no prompt injection attempts or instructions for the AI agent to perform malicious actions; instead, it promotes good security practices and provides examples of security tools. The `README.md` outlines standard installation procedures, including fetching from a public GitHub repository via `npx add`, which is a common method for skill distribution and does not inherently indicate malice in the skill's content itself. There is no evidence of data exfiltration, malicious execution, persistence, or obfuscation.