skills.rest
dimagi-internal
dimagi-internalOFFICIAL
Explore all skills by this author →
GitHub

app-release-qa

Detect structural and runtime defects in released CommCare CCZ artifacts.

1|2|Updated Apr 1, 2026
Search Tags:#ace#runtime validation#app release#commcare#structural qa#ccz#xpath binding
One-click install
npx skills add https://github.com/dimagi-internal/ace --skill app-release-qa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: app-release-qa
Source: https://github.com/dimagi-internal/ace/tree/main/skills/app-release-qa
Command: npx skills add https://github.com/dimagi-internal/ace --skill app-release-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Released CommCare CCZ artifacts often have undetected structural and runtime defects that pass earlier build validation gates (like validate_app and make_build) but cause on-device failures, broken HQ→Connect sync, or broken Phase 6 mobile testing. These defects include missing Connect markers, silent field omissions, incorrect geopoint bind types, and XPath form-init errors that are invisible to static checks.

Core Features & Use Cases

  • Structural CCZ Verification: Cross-references released Learn and Deliver CCZ contents against Nova app blueprints to verify form counts, Connect marker presence, per-form field counts, and geopoint bind type fidelity.
  • Runtime Install Validation: Runs commcare-cli validate and play checks to catch XPath binding failures that only surface at form-init time on CommCare mobile runtime.
  • Deterministic Gating: Produces a clear pass/fail verdict YAML with detailed per-app metrics, halting the ACE Phase 3 pipeline immediately on any blocker defect to prevent broken apps from progressing to later phases. Use case: For ACE teams building CommCare Connect apps, this skill eliminates the risk of shipping broken CCZ releases that would fail during user training, mobile deployment, or live operations.

Quick Start

Run the app-release-qa skill immediately after completing the Phase 3 app release step to automatically verify the structural integrity and install-time validity of the released Learn and Deliver CCZ artifacts, and halt the release pipeline if any defects are detected.

Frequently Asked Questions about app-release-qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I catch CommCare CCZ release defects that pass build validation but fail on-device?▼

To catch CommCare CCZ release defects, cross-reference released Learn and Deliver CCZ contents against Nova app blueprints and run commcare-cli runtime checks to detect missing Connect markers, silent field omissions, and XPath form-init binding failures.

How do I verify Connect markers and geopoint bind types in released CommCare apps?▼

Verify Connect markers and geopoint bind types by performing structural CCZ verification that cross-references released CCZ contents against Nova app blueprints to check form counts, per-form field counts, and geopoint bind type fidelity.

Why do CommCare apps fail HQ to Connect sync after passing static validation checks?▼

CommCare apps fail HQ to Connect sync because static validation gates miss runtime defects like missing Connect markers, silent field omissions, incorrect geopoint bind types, and XPath form-init errors that only surface during on-device installation.

When should I run runtime install validation for CommCare CCZ artifacts?▼

Run runtime install validation immediately after completing the ACE Phase 3 app release step to automatically verify structural integrity and install-time validity of released Learn and Deliver CCZ artifacts before progressing to later phases.

Can I use deterministic pass fail gating to halt the ACE Phase 3 pipeline on CCZ defects?▼

Yes, deterministic pass fail gating produces a clear verdict YAML with detailed per-app metrics, halting the ACE Phase 3 pipeline immediately on any blocker defect to prevent broken apps from progressing to later phases.

What is structural CCZ verification for CommCare Connect apps?▼

Structural CCZ verification is a deterministic process that cross-references released Learn and Deliver CCZ contents against Nova app blueprints to verify form counts, Connect marker presence, per-form field counts, and geopoint bind type fidelity.

Related Skills

Explore More Software Engineering Skills→
dimagi-internaldimagi-internal
1

app-release-eval

Grade release completeness of Learn and Deliver app builds across four weighted dimensions.

Official
Advanced
dimagi-internaldimagi-internal
1

fork-run

Fork ACE opportunity runs at skill boundaries to preserve upstream artifacts.

Official
Intermediate
dimagi-internaldimagi-internal
1

app-multimedia-coverage

Generate and integrate display images into CommCare Connect form questions.

Official
Advanced
krzemienskikrzemienski
2

build-quality-gates

Enforce sequential compile, lint, type-check, and bundle gates before deployment.

Community
Intermediate