网有NETHAVE
AGENT SKILL

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.

License 许可
MIT
最近更新
2026-11-14
Stars
★ 160
Forks
83

01 前言 Front Matter

name
recompile-workflows
description
Regenerate and post-process all agentic workflows. Use when gh-aw is updated, workflow .md files change, or when asked to recompile/regenerate workflows.
allowed-tools
Bash(gh:*), Bash(npx:*), Read, Glob, Edit

02 资源文件 500

03 SKILL.md 正文

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

04 同仓库更多 Skills

github
github/gh-aw-firewall

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.

测试与质量运维与部署
★ 160
github
github/gh-aw-firewall

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.

开发工程师测试与质量运维与部署
★ 160
github
github/gh-aw-firewall

sandbox-filesystem-access

Configure or diagnose file and directory access, mounts, and host ACLs for AWF sandboxes.

★ 160
github
github/gh-aw-firewall

pr-finisher

Prepare an open pull request for merge from a GitHub Copilot cloud agent. Drives Reviews, local validation, and Mergeable to a ready state. Does not merge, and cannot trigger CI.

★ 160
github
github/gh-aw-firewall

debugging-workflows

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

★ 160
github
github/gh-aw-firewall

agentic-workflows

Route gh-aw design, creation, diagnosis, patching, active debugging, upgrades, and local SDLC issue requests to the right strategies.

★ 160