app-release

Create versioned CommCare builds and release Learn and Deliver apps on CCHQ.

1|2|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/dimagi-internal/ace --skill app-release-dimagi-internal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-release
Source: https://github.com/dimagi-internal/ace/tree/main/skills/app-release
Command: npx skills add https://github.com/dimagi-internal/ace --skill app-release-dimagi-internal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the critical gap where Nova-uploaded CommCare apps exist only as unreleased drafts on CCHQ, preventing Connect from surfacing deliver units for opportunities and causing Phase 4 workflows to stall entirely.

Core Features & Use Cases

  • Automated Build & Release: Creates versioned builds and marks Learn and Deliver CommCare apps as released on CCHQ to make their form schemas visible to Connect.
  • Build Rejection Auto-Remediation: Includes a bounded retry loop that parses CCHQ build rejection errors, dispatches the Nova architect to fix invalid XForm issues in the source app, and re-uploads the corrected app to retry the build.
  • Post-Release Validation: Runs strict checks on released builds to catch Connect schema collisions, oversized slugs, and missing Connect metadata that would cause downstream Phase 4 failures. Use case example: When running the ACE lifecycle for a new Connect opportunity, use this skill immediately after app deployment to ensure the Learn and Deliver apps are properly released so deliver units appear in the opportunity wizard for payment unit configuration.

Quick Start

Use the app-release skill to build and release the Learn and Deliver CommCare apps for the current ACE opportunity run.

Frequently Asked Questions about app-release

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

FAQPage Schema
How do I release CommCare apps to surface Connect deliver units for an opportunity?

To release CommCare apps and surface Connect deliver units, you must create versioned builds and toggle the release status for Learn and Deliver app types on CommCare HQ. This skill automates that exact release process.

Why are Connect deliver units not showing up after uploading apps to CommCare HQ?

Connect deliver units do not appear because Nova-uploaded CommCare apps exist only as unreleased drafts on CCHQ. Releasing the draft app builds makes their form schemas visible to Connect, resolving the surfacing blocker.

How do I fix CommCare build rejection errors caused by invalid XForm schemas?

To fix CommCare build rejection errors, this skill parses the CCHQ rejection message, dispatches the Nova architect to edit invalid XForm issues in the source app, and re-uploads the corrected app to retry the build.

Does this app release process validate Connect slug collisions and metadata before Phase 4?

Yes, the app release process includes post-release validation that runs strict checks on released builds to catch Connect schema collisions, oversized slugs, and missing Connect metadata that would cause downstream Phase 4 failures.

Can I use this skill to automate CCHQ endpoint interactions for app deployment?

Yes, you can use this skill to automate CCHQ endpoint interactions for app deployment. It handles CSRF-authenticated CCHQ endpoint communication to create builds, toggle release status, and trigger downstream deliver unit syncs.

What is the best way to handle CommCare app releases within ACE Phase 3 workflows?

The best way to handle CommCare app releases within ACE Phase 3 workflows is to automate build creation, release status toggling, and schema validation. This ensures released Learn and Deliver apps properly trigger Phase 4 deliver unit syncs.