asc-workflow CLI 工作流自动化工具：本地与 CI 流水线任务管理

asc-workflow by rudrankriyam/asc-skills

291 周安装量

663 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/rudrankriyam/asc-skills --skill asc-workflow

自动化开发运维命令行工具

🇨🇳中文介绍

asc workflow

当您需要在 CLI 中使用流水线式自动化时，请使用此技能，涉及以下命令：

asc workflow run
asc workflow validate
asc workflow list

此功能最适合那些存在于您的代码仓库中、可在 PR 中审查、并且可以在本地和 CI 中以相同方式运行的确定性自动化任务。

命令发现

始终使用 --help 来确认标志和子命令：
- asc workflow --help
- asc workflow run --help
- asc workflow validate --help

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

相关 Skills

FlyClaw：零登录航班聚合查询工具，Python实现多源航班信息与价格搜索

4,000,000 周安装

Vercel React 最佳实践指南 | 58条Next.js性能优化规则与代码重构

269,400 周安装

agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试

147,400 周安装

Azure RBAC 权限管理工具：查找最小角色、创建自定义角色与自动化分配

117,000 周安装

编写 .asc/workflow.json
验证结构和引用：
- asc workflow validate
发现可用的工作流：
- asc workflow list
- asc workflow list --all (包含私有辅助工作流)
预览执行（无副作用）：
- asc workflow run --dry-run beta
使用运行时参数执行：
- asc workflow run beta BUILD_ID:123456789 GROUP_ID:abcdef

stdout：结构化的 JSON 结果 (status、steps、持续时间)
stderr：步骤命令输出、钩子输出、dry-run 预览
asc workflow validate 始终打印 JSON，并在无效时返回非零值

env：全局默认值
before_all：在步骤之前运行一次的指令
after_all：在步骤成功后运行一次的指令
error：当任何失败发生时运行的指令
workflows：命名工作流映射

字符串简写："echo hello" -> 运行步骤
对象形式：
- run：shell 命令
- workflow：调用子工作流
- name：用于报告的标签
- if：条件变量名
- with：仅用于工作流调用步骤的环境变量覆盖

asc workflow run <name> [KEY:VALUE ...] 支持两种分隔符：
- VERSION:2.1.0
- VERSION=2.1.0
如果两种分隔符都存在，则第一个生效。
重复的键遵循“最后写入优先”原则。
在步骤命令中，通过 shell 扩展 ($VAR) 引用参数。
避免将密钥放在 .asc/workflow.json 中；通过 CI 密钥/环境变量传递它们。

使用 "workflow": "<name>" 来调用辅助工作流。
使用 "private": true 来标记仅供辅助使用的工作流。
私有工作流：
- 不能直接运行
- 可以被其他工作流调用
- 在 asc workflow list 中隐藏，除非使用 --all
验证会捕获未知的工作流引用和循环引用。

在步骤上添加 "if": "VAR_NAME"。
仅当 VAR_NAME 为真值时，步骤才会运行。
真值：1、true、yes、y、on (不区分大小写)。
if 查找的解析顺序：
1. 合并后的工作流环境变量/参数
2. os.Getenv(VAR_NAME)

将工作流文件保存在版本控制中。
在步骤命令中尽可能使用 ID 以实现确定性自动化。
在步骤内部进行破坏性的 asc 操作时使用 --confirm。
先验证，然后 dry-run，最后再实际运行。
保持钩子轻量级并注意副作用。

{ "env": { "APP_ID": "123456789", "VERSION": "1.0.0" }, "before_all": "asc auth status", "after_all": "echo workflow_done", "error": "echo workflow_failed", "workflows": { "beta": { "description": "将构建版本分发到 TestFlight 群组并通知", "env": { "GROUP_ID": "" }, "steps": [ { "name": "list_builds", "run": "asc builds list --app $APP_ID --sort -uploadedDate --limit 5" }, { "name": "list_groups", "run": "asc testflight groups list --app $APP_ID --limit 20" }, { "name": "add_build_to_group", "if": "BUILD_ID", "run": "asc builds add-groups --build $BUILD_ID --group $GROUP_ID" }, { "name": "notify", "if": "SLACK_WEBHOOK", "run": "echo sent_release_notice" } ] }, "release": { "description": "提交版本以供 App Store 审核", "steps": [ { "workflow": "sync-metadata", "with": { "METADATA_DIR": "./metadata" } }, { "name": "submit", "run": "asc submit create --app $APP_ID --version $VERSION --build $BUILD_ID --confirm" } ] }, "sync-metadata": { "private": true, "description": "私有辅助工作流（仅可通过工作流步骤调用）", "steps": [ { "name": "migrate_validate", "run": "echo METADATA_DIR_is_$METADATA_DIR" } ] } } }

# 验证并在文件无效时使 CI 失败
asc workflow validate | jq -e '.valid == true'

# 显示可发现的工作流
asc workflow list --pretty

# 包含私有辅助工作流
asc workflow list --all --pretty

# 预览实际运行
asc workflow run --dry-run beta BUILD_ID:123 GROUP_ID:grp_abc

# 使用参数运行并断言成功
asc workflow run beta BUILD_ID:123 GROUP_ID:grp_abc | jq -e '.status == "ok"'

🇺🇸English

asc workflow

Use this skill when you need lane-style automation inside the CLI using:

asc workflow run
asc workflow validate
asc workflow list

This feature is best for deterministic automation that lives in your repo, is reviewable in PRs, and can run the same way locally and in CI.

Command discovery

Always use --help to confirm flags and subcommands:
- asc workflow --help
- asc workflow run --help
- asc workflow validate --help
- asc workflow list --help

End-to-end flow

Author .asc/workflow.json
Validate structure and references:
- asc workflow validate
Discover available workflows:
- asc workflow list
- asc workflow list --all (includes private helpers)
Preview execution without side effects:
- asc workflow run --dry-run beta
Execute with runtime params:
- asc workflow run beta BUILD_ID:123456789 GROUP_ID:abcdef

File location and format

Default path: .asc/workflow.json
Override path: asc workflow run --file ./path/to/workflow.json <name>
JSONC comments are supported (// and /* ... */)

Output and CI contract

stdout: structured JSON result (status, steps, durations)
stderr: step command output, hook output, dry-run previews
asc workflow validate always prints JSON and returns non-zero when invalid

This enables machine-safe checks:

asc workflow validate | jq -e '.valid == true'
asc workflow run beta BUILD_ID:123 GROUP_ID:xyz | jq -e '.status == "ok"'

Schema (what the feature supports)

Top-level keys:

env: global defaults
before_all: command run once before steps
after_all: command run once after successful steps
error: command run when any failure occurs
workflows: named workflow map

Workflow keys:

description
private (not directly runnable)
env
steps

Step forms:

String shorthand: "echo hello" -> run step
Object with:
- run: shell command
- workflow: call sub-workflow
- name: label for reporting
- if: conditional var name
- with: env overrides for workflow-call steps only

Runtime params (`KEY:VALUE` / `KEY=VALUE`)

asc workflow run <name> [KEY:VALUE ...] supports both separators:
- VERSION:2.1.0
- VERSION=2.1.0
If both separators exist, the first one wins.
Repeated keys are last-write-wins.
In step commands, reference params via shell expansion ($VAR).
Avoid putting secrets in .asc/workflow.json; pass them via CI secrets/env.

Run-tail flags

asc workflow run also accepts core flags after the workflow name:

--dry-run
--pretty
--file

Examples:

asc workflow run beta --dry-run
asc workflow run beta --file .asc/workflow.json BUILD_ID:123

Execution semantics

before_all runs once before step execution
after_all runs only when steps succeed
error runs on failure (step failure, before/after hook failure)
Sub-workflows are executed inline as part of the call step
Maximum sub-workflow nesting depth is 16

Env precedence

Main workflow run:

definition.env < workflow.env < CLI params

Sub-workflow call step ("workflow": "...", "with": {...}):

sub-workflow env defaults
caller env (including CLI params) overrides
step with overrides all

Sub-workflows and private workflows

Use "workflow": "<name>" to call helper workflows.
Use "private": true for helper-only workflows.
Private workflows:
- cannot be run directly
- can be called by other workflows
- are hidden from asc workflow list unless --all is used
Validation catches unknown workflow references and cyclic references.

Conditionals (`if`)

Add "if": "VAR_NAME" on a step.
Step runs only if VAR_NAME is truthy.
Truthy: 1, true, yes, y, on (case-insensitive).
Resolution order for if lookup:
1. merged workflow env/params
2. os.Getenv(VAR_NAME)

Dry-run behavior

asc workflow run --dry-run <name> does not execute commands.
It prints previews to stderr.
Dry-run shows raw commands (without env expansion), which helps avoid secret leakage in previews.

Shell behavior

Run steps use bash -o pipefail -c when bash is available.
Fallback is sh -c when bash is unavailable.
Pipelines therefore fail correctly in most CI shells when bash exists.

Practical authoring rules

Keep workflow files in version control.
Use IDs in step commands where possible for deterministic automation.
Use --confirm for destructive asc operations inside steps.
Validate first, then dry-run, then real run.
Keep hooks lightweight and side-effect aware.

{ "env": { "APP_ID": "123456789", "VERSION": "1.0.0" }, "before_all": "asc auth status", "after_all": "echo workflow_done", "error": "echo workflow_failed", "workflows": { "beta": { "description": "Distribute a build to a TestFlight group and notify", "env": { "GROUP_ID": "" }, "steps": [ { "name": "list_builds", "run": "asc builds list --app $APP_ID --sort -uploadedDate --limit 5" }, { "name": "list_groups", "run": "asc testflight groups list --app $APP_ID --limit 20" }, { "name": "add_build_to_group", "if": "BUILD_ID", "run": "asc builds add-groups --build $BUILD_ID --group $GROUP_ID" }, { "name": "notify", "if": "SLACK_WEBHOOK", "run": "echo sent_release_notice" } ] }, "release": { "description": "Submit a version for App Store review", "steps": [ { "workflow": "sync-metadata", "with": { "METADATA_DIR": "./metadata" } }, { "name": "submit", "run": "asc submit create --app $APP_ID --version $VERSION --build $BUILD_ID --confirm" } ] }, "sync-metadata": { "private": true, "description": "Private helper workflow (callable only via workflow steps)", "steps": [ { "name": "migrate_validate", "run": "echo METADATA_DIR_is_$METADATA_DIR" } ] } } }

Useful invocations

# Validate and fail CI on invalid file
asc workflow validate | jq -e '.valid == true'

# Show discoverable workflows
asc workflow list --pretty

# Include private helpers
asc workflow list --all --pretty

# Preview a real run
asc workflow run --dry-run beta BUILD_ID:123 GROUP_ID:grp_abc

# Run with params and assert success
asc workflow run beta BUILD_ID:123 GROUP_ID:grp_abc | jq -e '.status == "ok"'

Weekly Installs

217

Repository

rudrankriyam/asc-skills

GitHub Stars

593

First Seen

Feb 19, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

codex216

opencode197

gemini-cli195

kimi-cli195

github-copilot195

amp195

asc-workflow CLI 工作流自动化工具：本地与 CI 流水线任务管理

🇨🇳中文介绍

asc workflow

命令发现

相关 Skills

端到端流程

文件位置和格式

输出和 CI 契约

模式（该功能支持的内容）

运行时参数 (`KEY:VALUE` / `KEY=VALUE`)

运行尾部标志

执行语义

环境变量优先级

子工作流和私有工作流

条件语句 (`if`)

Dry-run 行为

Shell 行为

实用的编写规则

有用的调用示例

🇺🇸English

asc workflow

Command discovery

End-to-end flow

File location and format

Output and CI contract

Schema (what the feature supports)

Runtime params (`KEY:VALUE` / `KEY=VALUE`)

Run-tail flags

Execution semantics

Env precedence

Sub-workflows and private workflows

Conditionals (`if`)

Dry-run behavior

Shell behavior

Practical authoring rules

Useful invocations

最新 Skills

asc-workflow CLI 工作流自动化工具：本地与 CI 流水线任务管理

🇨🇳中文介绍

asc workflow

命令发现

相关 Skills

端到端流程

文件位置和格式

输出和 CI 契约

模式（该功能支持的内容）

运行时参数 (KEY:VALUE / KEY=VALUE)

运行尾部标志

执行语义

环境变量优先级

子工作流和私有工作流

条件语句 (if)

Dry-run 行为

Shell 行为

实用的编写规则

有用的调用示例

🇺🇸English

asc workflow

Command discovery

End-to-end flow

File location and format

Output and CI contract

Schema (what the feature supports)

Runtime params (KEY:VALUE / KEY=VALUE)

Run-tail flags

Execution semantics

Env precedence

Sub-workflows and private workflows

Conditionals (if)

Dry-run behavior

Shell behavior

Practical authoring rules

Useful invocations

最新 Skills

运行时参数 (`KEY:VALUE` / `KEY=VALUE`)

条件语句 (`if`)

Runtime params (`KEY:VALUE` / `KEY=VALUE`)

Conditionals (`if`)