asc-workflow

Define, validate, and execute JSONC workflow automations in repositories.

32|10|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/moasq/nanowave --skill asc-workflow-moasq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-workflow
Source: https://github.com/moasq/nanowave/tree/main/internal/orchestration/skills/features/asc-workflow
Command: npx skills add https://github.com/moasq/nanowave --skill asc-workflow-moasq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines complex, multi-step release and CI/CD processes by defining them as code within your repository, ensuring consistency and repeatability.

Core Features & Use Cases

  • Define Automations: Create declarative workflows in .asc/workflow.json for tasks like building, testing, and deploying.
  • Validate & Run: Validate workflow syntax and execute them locally or in CI using asc workflow.
  • Use Case: Automate the entire process of building a new version of your app, running integration tests, and deploying it to TestFlight, all triggered by a single command.

Quick Start

Validate your workflow configuration file using asc workflow validate.

Frequently Asked Questions about asc-workflow

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

FAQPage Schema
How do I define and run repo-local CI/CD workflows as code?

Repo-local CI/CD workflows are defined using JSONC-formatted workflow definitions in a configuration file, then validated and executed locally or within a CI environment using a command-line orchestration tool.

Can I automate multi-step release processes with shell commands and conditionals?

Multi-step release processes support shell commands, sub-workflow calls, and environment variable management, executing conditionally with hooks to ensure deterministic and repeatable pipeline automation.

How do I validate my CI pipeline orchestration configuration syntax?

CI pipeline orchestration configurations are validated by running a specific command-line validation tool against the JSONC workflow definition file to check syntax before execution.

Is it possible to migrate from legacy lane tools to declarative release management workflows?

Migration from legacy lane tools to declarative release management workflows is supported natively, allowing transition to JSONC-based definitions for building, testing, and deploying applications.

What is the best way to orchestrate deterministic environment variables across sub-workflow calls?

Deterministic environment variable orchestration across sub-workflow calls is managed natively within the JSONC workflow definition, ensuring consistent execution context for automation scripts.