asc-workflow

Automate in-repo multi-step workflows with frontmatter-based metadata and deterministic runtime.

33|2|Updated Feb 21, 2025
One-click install
npx skills add https://github.com/yspreen/dotfiles --skill asc-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-workflow
Source: https://github.com/yspreen/dotfiles/tree/main/.agents/skills/asc-workflow
Command: npx skills add https://github.com/yspreen/dotfiles --skill asc-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation, validation, and execution of in-repo multi-step workflows to ensure consistent automation across local development and CI pipelines.

Core Features & Use Cases

  • Deterministic in-repo automation: author, validate, and run workflows within the repository, enabling version-controlled, auditable pipelines.
  • Support for sub-workflows and hooks: orchestrate nested steps with conditional execution and pre/post hooks for complex release flows.
  • Migration and collaboration: bridge from lane tools and wire CI pipelines to coordinate release tasks across teams.

Quick Start

Create or edit the .asc/workflow.json file to define your first workflow, then run asc workflow validate to verify its structure.

Frequently Asked Questions about asc-workflow

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

FAQPage Schema
How do I automate in-repo workflows for local development and CI pipelines?

Automating in-repo workflows involves authoring multi-step tasks using frontmatter-based metadata files to ensure deterministic runtime execution across local development and CI pipelines. This enables version-controlled, auditable pipelines to run reliably.

What is the best way to coordinate release tasks with sub-workflows?

Coordinating release tasks with sub-workflows requires an in-repo automation workflow that orchestrates nested steps with conditional execution and pre/post hooks. This manages complex release flows deterministically within the repository.

How do I migrate from lane tools to a repository-local automation workflow?

To migrate from lane tools to a repository-local automation workflow, you define your multi-step processes in a local metadata file. This bridges existing tasks to a deterministic, version-controlled pipeline structure within the repository.

How do I validate the structure of an in-repo automation workflow?

You validate an in-repo automation workflow by running the validation command against your defined metadata file. This verifies the frontmatter-based structure and ensures the deterministic runtime execution requirements are satisfied before running.

Does this in-repo workflow automation support pre and post hooks for CI pipelines?

Yes, in-repo workflow automation supports pre and post hooks for CI pipelines. It orchestrates nested steps with conditional execution and hooks to manage complex release flows reliably across teams.

When do I need deterministic runtime for repository-local automation?

Deterministic runtime for repository-local automation is needed when wiring CI pipelines and coordinating release tasks across teams. It ensures consistent, auditable execution of multi-step workflows from local development to production.