English | Chinese (Simplified)

Stop writing GitHub workflow automation from scratch.

56 ready-to-use GitHub Agentic Workflow templates — copy one, adapt three lines, and your repository handles issue triage, PR review, release notes, and secret detection automatically. Each template is written around one narrow maintainer outcome, tested against the current gh-aw CLI, and designed to be audited in under a minute.

Requires: GitHub Agentic Workflows (currently in technical preview). These are not standard GitHub Actions YAML workflows — they use the gh aw CLI to compile Markdown into runnable workflows.

Works on macOS, Linux, and Windows.

# 1. Pick a template from the library below and copy it to your repo
cp templates/issue-management/auto-triage.md /your-repo/.github/workflows/auto-triage.md

# 2. Edit the three repository-specific lines (labels, ownership rules, instructions)
# 3. Validate and compile
gh aw validate --dir .github/workflows
gh aw compile  --dir .github/workflows

# 4. Commit both the .md source and the generated .lock.yml

Or add directly from GitHub:

gh aw add OneRose328/awesome-agentic-workflows/templates/issue-management/auto-triage.md

Pick the row that matches your situation. These are the highest-leverage, lowest-risk entry points:

Rollout advice: Start with one workflow that only comments or drafts. Prove it's low-noise in your repository before enabling anything that labels or routes automatically.

templates/issue-management/auto-triage.md   ← this repo (what you copy and edit)
.github/workflows/auto-triage.md            ← your repo (your customized source)
.github/workflows/auto-triage.lock.yml      ← your repo (compiled, do not hand-edit)

Edit the .md source. Run gh aw compile. Commit both files. Never hand-edit .lock.yml.

Do I need GitHub Copilot to use these templates?

No. You need the GitHub Agentic Workflows toolchain, but the workflow engine can still vary by setup. These templates are about workflow structure and task design, not a Copilot-only feature pack.

Can I use the templates exactly as they are?

Usually not. They are strong starting points, but you should still replace labels, paths, ownership rules, and repository-specific instructions before treating them as production-ready.

Do I edit the .lock.yml file?

No. Treat the Markdown .md file as the source you edit. The .lock.yml file is the compiled output generated from that source.

Are these templates safe to run in production immediately?

They are written around safer defaults, but you should still start with low-risk workflows, validate them, compile them, and test them in a controlled repository context before broad use.

Do I need all 56 templates?

No. Most repositories should start with one or two low-risk workflows and only expand once the first ones are predictable and useful.

Why keep templates in templates/ if real workflows live in .github/workflows/?

Because this repository is a library. templates/ is the catalog of reusable source templates. In your own repository, the workflows you actually run belong in .github/workflows/.

This repository is aligned with the public GitHub Agentic Workflows documentation available on March 1, 2026. Because the feature is still in early development, re-check the official docs before enabling a workflow in production.

For current behavior, re-check these official references before making compatibility-sensitive changes:

• CLI Commands
• Creating Agentic Workflows
• Workflow Structure

This repository is meant to be maintained, not dumped once and abandoned.

• PATCH releases fix wording, docs, and compatibility details without materially changing the template catalog.
• MINOR releases add templates or meaningfully expand existing workflows.
• MAJOR releases reflect breaking changes in structure or compatibility assumptions.
• When GitHub Agentic Workflows changes, verify the current official docs first, then note the compatibility update in CHANGELOG.md and reflect it in the next release notes.
• Before updating templates already in use, update the source .md, re-run gh aw validate --dir templates/<category> from the repository root, and recompile any affected example workflows before merging.

See CONTRIBUTING.md for the authoring checklist, structure rules, and validation expectations.

This repository is set up to keep contribution review lightweight:

• .github/pull_request_template.md asks contributors to explain what changed and what they validated
• .github/workflows/validate.yml checks template structure on pushes and pull requests

The intent is simple: use CI and clear pull request scope as the hard merge gates, and keep review expectations easy to understand.

Released under the MIT License.