YAGA documentation¶
YAGA checks repository conventions locally and in CI: commit messages, branch names, changes, committed files, and GitHub Actions workflows. You choose the checks and supply their inputs.
Install and run your first check Find a command
New to YAGA?¶
Evaluating it for an existing repository? Assess and adopt in CI maps problems to capabilities, prerequisites, and integration steps.
- Get started: install the CLI, inspect or create a policy, and check a commit.
- Choose an adoption recipe: add a local hook or an ordinary CI check.
- Create a repository plan: keep a repeatable set of checks once you need several.
Find the reference you need¶
| Working on | Read |
|---|---|
| Message structure, bodies, footers, or spelling | Commit policy |
| Policy discovery and configuration keys | Configuration |
| Branch names, changes, or committed files | Repository checks |
| Workflow references, permissions, or syntax | Workflow checks |
| Pull-request validation | GitHub Actions |
| A failing command or missing prerequisite | Troubleshooting |
Usage modes explains where local commands, hooks, and CI fit together. The command index links each command to its detailed reference.
Optional review tools¶
Deterministic checks work without a model or review service. If you need additional review, see commit quality advice or agent review plans and receipts. The GitHub review adapter is experimental and requires a separate trusted-workflow deployment.
Project information¶
YAGA is beta. See the changelog, security model, contributor guide, and release procedure.