oe-release-readiness

shami-ah's avatarfrom shami-ah

Pre-merge/release readiness checklist for OpenEvent-AI. Use when preparing a PR for production: run the fastest validation lanes first (compile/import, smoke suite, deterministic site-visit trace), then escalate to full suites or integration checks as needed.

⭐0stars🔀1forks📁View on GitHub🕐Updated Jan 8, 2026⬇️1downloads
[Testing and QA]

When & Why to Use This Skill

This Claude skill automates the pre-merge and release readiness process for OpenEvent-AI projects. It optimizes the development lifecycle by implementing a tiered validation strategy, ensuring code stability through fast smoke tests, API regression checks, and hygiene audits before production deployment. By prioritizing fast gates and escalating to full suites only when necessary, it significantly reduces the feedback loop for developers while maintaining high software quality standards.

Use Cases

  • Pre-merge Validation: Quickly verify code integrity using fast gates like compilation checks and smoke suites before submitting Pull Requests to catch immediate regressions.
  • Regression Testing: Execute automated API and site-visit trace contracts to ensure new changes don't break existing agent-facing functionalities or tool parity.
  • Code Hygiene Audit: Maintain production-grade standards by automatically scanning for and removing debug prints or 'LLM-ish' artifacts in the runtime codebase.
  • Release Readiness Check: Perform a comprehensive final validation, including full integration suites and workflow logic checks, to guarantee a stable production release.
nameoe-release-readiness
description"Pre-merge/release readiness checklist for OpenEvent-AI. Use when preparing a PR for production: run the fastest validation lanes first (compile/import, smoke suite, deterministic site-visit trace), then escalate to full suites or integration checks as needed."

oe-release-readiness

Fast gates (run in this order)

  1. Compile/import + refactor invariants:

    • python3 scripts/verify_refactor.py

  2. Fast backend smoke suite (Step 1–7 core invariants):

    • ./scripts/test-smoke.sh

  3. Agent-facing API regressions (manager approve path + tool parity):

    • pytest backend/tests/agents/ -q

  4. Deterministic site-visit trace contract (no UI required):

    • python3 scripts/manual_ux_scenario_I.py > /tmp/ux_site_visit_I.json
    • python3 scripts/validate_manual_ux_run.py /tmp/ux_site_visit_I.json --require_site_visit

Full gates (only if the change touches workflow logic)

  • Full test suite:
    • ./scripts/test-all.sh

Hygiene gates (quick checks that prevent “LLM-ish” regressions)

  • No new debug prints in runtime code (allow scripts/tests only):
    • rg -n "print\\(" backend -g"*.py" | rg -v "/tests/|/scripts/|__init__\\.py"

Claude Code shortcut

  • Keep .claude/commands/validate.md up to date and run /validate for a full-stack lane.