Update to Vibe Coding

{
  "description": "Audit test coverage or release readiness, improve an existing test harness, or verify visual regressions. For review of a concrete diff use vibe-review.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 206
    },
    {
      "relative_path": "references/release-readiness-audit.md",
      "size_in_bytes": 2900
    },
    {
      "relative_path": "references/test-coverage-audit.md",
      "size_in_bytes": 2905
    },
    {
      "relative_path": "references/test-harness-polish.md",
      "size_in_bytes": 1235
    },
    {
      "relative_path": "references/visual-regression-check.md",
      "size_in_bytes": 1212
    }
  ],
  "name": "vibe-quality",
  "skill_md_contents": "---\nname: vibe-quality\ndescription: \"Audit test coverage or release readiness, improve an existing test harness, or verify visual regressions. For review of a concrete diff use vibe-review.\"\n---\n\n# Quality & readiness\n\nRead [the shared workflow](../../references/workflow.md) once per task, then the one recipe matching the requested operation and boundary. Do not load every recipe. The user's request controls scope and whether edits are allowed.\n\nThis covers verification quality and release assessment. It does not grant release/deployment permission. A visual result needs rendered evidence; code inspection alone is not visual verification.\n\n## Recipes\n\n| Recipe | Operation |\n|---|---|\n| [Release Readiness Audit](references/release-readiness-audit.md) | audit |\n| [Test Coverage Audit](references/test-coverage-audit.md) | audit |\n| [Test Harness Polish](references/test-harness-polish.md) | implement |\n| [Visual Regression Check](references/visual-regression-check.md) | check |\n\nFor an explicit multi-stage request, follow the necessary stages without discarding requested work. For a single stage, deliver that result and stop. Use [the catalog](../../references/catalog.md) only if the requested boundary belongs elsewhere.\n"
}