跳到正文
cccskills
免费在 GitHub 公开

recompile-workflows

Regenerate and post-process all agentic workflows. Use when gh-aw is updated, workflow .md files change, or when asked to recompile/regenerate workflows.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md2.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Recompile Agentic Workflows

Use this skill when you need to regenerate all agentic workflow lock files and apply post-processing.

IMPORTANT: Post-processing is required after EVERY lock file change

Any time .lock.yml files are regenerated — whether via gh aw compile, gh aw upgrade, or any other gh-aw command — you MUST run the post-processing script afterward. This is not optional.

Steps

1. Compile or upgrade workflows

Use whichever command is appropriate:

# Full upgrade (updates agents, actions, codemods, then compiles)
gh aw upgrade

# Just recompile (when only .md workflow files changed)
gh aw compile

If any workflow fails to compile (e.g., strict mode violations like contents: write), fix the .md source file and re-run.

2. Run post-processing script (ALWAYS)

This step MUST run every time lock files are regenerated, regardless of how they were generated.

The post-processing script replaces the "Install awf binary" step in smoke and build-test workflows with local build+install steps, so CI tests the repo's own code instead of a released binary.

npx ts-node scripts/ci/postprocess-smoke-workflows.ts

This updates these lock files:

  • smoke-copilot.lock.yml
  • smoke-claude.lock.yml
  • smoke-chroot.lock.yml
  • build-test.lock.yml

Common Issues

Strict mode violations

Newer gh-aw versions enforce strict mode which disallows write permissions like contents: write, issues: write, etc. Workflows should use safe-outputs for write operations and only request read permissions.

Discussion category warnings

Warnings about "General" vs "general" discussion category casing are non-blocking.

Verification

After both steps, run git diff --stat to review all changed files. Expect changes in:

  • .github/agents/ - Updated agent files
  • .github/aw/actions-lock.json - Updated action pins
  • .github/workflows/*.lock.yml - Regenerated lock files
  • .github/workflows/*.md - If codemods applied fixes

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Decide and implement how to support a new LLM provider or agent engine in AWF - either as a proxied provider (api-proxy adapter) or a direct-API engine (domain allowlist only), e.g. Cursor, Aider, or any tool that calls its own endpoint.

中文简介正在准备中。当前显示原文说明。

github/gh-aw-firewall1502026年10月20日 更新

Route gh-aw design, creation, diagnosis, patching, active debugging, and upgrade requests to the right strategies.

中文简介正在准备中。当前显示原文说明。

github/gh-aw-firewall1502026年10月20日 更新

Practical Python scripts for debugging awf - parse logs, diagnose issues, inspect containers, test domains

中文简介正在准备中。当前显示原文说明。

github/gh-aw-firewall1502026年10月20日 更新

awf-skill

免费

Use the AWF (Agentic Workflow Firewall) to run commands with network isolation and domain whitelisting. Provides L7 HTTP/HTTPS egress control for AI agents.

中文简介正在准备中。当前显示原文说明。

github/gh-aw-firewall1502026年10月20日 更新

Debug the AWF firewall by inspecting Docker containers (awf-squid, awf-agent), analyzing Squid access logs, checking iptables rules, and troubleshooting blocked domains or network issues.

中文简介正在准备中。当前显示原文说明。

github/gh-aw-firewall1502026年10月20日 更新

Debug GitHub Actions workflows by downloading logs, analyzing summaries, and understanding how agentic workflows and the AWF firewall work together.

中文简介正在准备中。当前显示原文说明。

github/gh-aw-firewall1502026年10月20日 更新

查看 github 的全部技能

报告此技能的问题