GitHub Agentic Workflows

Procedures

Step 1: Identify the repository state

1. Inspect the workspace for .github/workflows/, .github/agents/, existing .lock.yml files, and any gh aw usage.
2. Execute node skills/github-agentic-workflows/scripts/find-gh-aw-targets.mjs . when a Node runtime is available.
3. Run gh aw version before making compiler-sensitive decisions so the workflow authoring path matches the installed CLI behavior.
4. If the repository contains multiple candidate workflows, prefer the workflow the user named or the one closest to the active issue, pull request, or automation surface.
5. If the repository has no GH-AW setup and the task is to create or maintain agentic workflows, read references/authoring.md before editing.
6. If the task is limited to standard deterministic GitHub Actions YAML without agentic markdown workflows, stop and explain that this skill does not apply.

Step 2: Choose the working mode

1. Classify the task as one of: repository setup, new workflow authoring, workflow revision, workflow installation from another repository, security review, or failure debugging.
2. Read references/examples.md when the task needs a starting pattern for scheduled reports, issue or PR triage, orchestration, or agent handoff.
3. Read references/security-and-operations.md when the workflow needs safe outputs, network policy, authentication, lockdown, threat detection, or run observability.
4. Read references/troubleshooting.md when the workflow fails to compile, install, authenticate, execute safe outputs, or access tools.