asc-workflow

Define, validate, and execute workflows from .asc/workflow.json.

1|Updated Aug 16, 2025
One-click install
npx skills add https://github.com/barronlroth/Cubby --skill asc-workflow-barronlroth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-workflow
Source: https://github.com/barronlroth/Cubby/tree/main/.agents/skills/asc-workflow
Command: npx skills add https://github.com/barronlroth/Cubby --skill asc-workflow-barronlroth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates repo-local multi-step automations to standardize and speed up development workflows inside a project.

Core Features & Use Cases

  • Define, validate, and execute workflows stored in .asc/workflow.json to orchestrate complex release and CI tasks.
  • Run, list, and dry-run workflows to preview actions without side effects; support for private helper workflows and sub-workflows.
  • Integrate with existing CLI tooling to migrate from older lane-style tools and enforce repeatable automation across environments.

Quick Start

Create a .asc/workflow.json in your repository and run asc workflow validate to confirm structure before executing a named workflow with asc workflow run.

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 automations for CI pipelines?

Repo-local automations are defined in a .asc/workflow.json file using JSONC format, then executed via the CLI command asc workflow run. You can validate the structure first with asc workflow validate to ensure the multi-step pipeline is configured correctly before execution.

Can I dry-run a workflow to preview CI actions without side effects?

Yes, you can use the asc workflow dry-run command to preview workflow actions without triggering actual side effects. This allows you to safely test multi-step automations, conditionals, and hooks before applying them to your build-release pipeline.

What is the best way to migrate from lane tools to repeatable repo workflows?

Migrating from lane-style tools involves defining your existing multi-step automations in a .asc/workflow.json file. The CLI integrates with existing tooling to orchestrate repeatable workflows, replacing older lane tools with standardized repo-local automation.

Does asc workflow support sub-workflows and private helper automations?

Yes, the workflow system supports both sub-workflows and private helper workflows. You can orchestrate complex release and CI tasks by nesting automations, applying conditionals, and using hooks to manage repeatable build-release flows.

How do I list available workflows in my repository?

You can list available workflows by running the asc workflow list command in your CLI. This displays all defined automations from your .asc/workflow.json file, including runnable workflows and private helper workflows.

Why should I validate my workflow JSON before running automations?

Validating your workflow JSON with asc workflow validate confirms the structural integrity of your .asc/workflow.json file before execution. This prevents pipeline failures by catching configuration errors in hooks, conditionals, and multi-step definitions early.