What problem does it solve?
Adding a new AI agentic engine to gh-aw requires choosing between a declarative shared engine definition, extending the behavior-defined runtime, or writing a dedicated Go engine, and each path involves catalog registration, smoke workflows, schema updates, and focused tests that are easy to miss.
Core Features & Use Cases
- Implementation Path Selection: Decision table for choosing between a shared Markdown engine definition, extending the declarative behavior model, or a dedicated Go engine registered in
pkg/workflow/agentic_engine.go.
- Declarative Engine Authoring: Step-by-step guidance for creating
.github/workflows/shared/<engine>.md definitions with pinned installation, execution, MCP, network, and log-parsing behaviors, plus engines.json registration and smoke workflows.
- Testing and Validation Guidance: Maps each changed behavior to the correct Go test files and prescribes
make build, make recompile, and agent progress-report commands.
- Use Case: When adding support for a new AI coding CLI to gh-aw, follow this Skill to declare its installation and execution behaviors, register it in the engine catalog, add a smoke workflow, and run the matching focused tests.
Quick Start
Ask the agent to add a new agentic engine definition for your CLI tool to gh-aw following the custom engine implementation guidelines.