asc-workflow

Automates multi-step workflows in ASC CLI with hooks and YAML frontmatter entry requirements.

4|Updated Dec 8, 2019
One-click install
npx skills add https://github.com/Detrous/dotfiles --skill asc-workflow-detrous
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-workflow
Source: https://github.com/Detrous/dotfiles/tree/main/claude/skills/asc-workflow
Command: npx skills add https://github.com/Detrous/dotfiles --skill asc-workflow-detrous

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define, validate, and run deterministic, repo-local automation workflows inside the CLI to streamline development, CI, and release pipelines.

Core Features & Use Cases

  • CLI-based automation: create lane-style automation inside the repository and run via asc workflow run, validate, and list.
  • End-to-end flow: author, validate, discover, preview, and execute workflows with environment and parameter support.
  • Sub-workflows and conditionals: support nested workflows, private helpers, and conditional step execution with if guards.

Quick Start

Create a .asc/workflow.json, then validate it and run a named workflow with parameters.

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 workflows inside the CLI?

You can define repo-local CI workflows by creating a .asc/workflow.json file, validating it, and executing it with runtime parameters using the CLI workflow run command.

What is the best way to orchestrate multi-step release pipelines with conditionals?

Orchestrating multi-step release pipelines is handled by defining deterministic shell flows with if guards, environment support, and nested sub-workflows to manage conditional step execution.

Can I use sub-workflows and runtime parameters for CLI automation?

Yes, CLI automation supports runtime parameters and nested sub-workflows, allowing you to execute structured workflows with dynamic inputs and private helpers for complex orchestration.

Does this workflow automation tool require external dependencies?

No, this workflow automation tool has zero external dependencies and operates entirely repo-local, validating and running workflows with structured JSON output directly inside the CLI.

How do I migrate from lane tooling to deterministic CLI workflows?

Migrating from lane tooling involves authoring lane-style automations as a JSON file with YAML-frontmatter, then discovering, previewing, and executing them as deterministic repo-local workflows.