Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.
Shows what the user's local repositories say about how they work, read from git and CI files on this machine with no GitHub token or network: follow-up fixes, CI trial and error, AI co-authorship, workflow hygiene, tests and loose ends. Use when GitHub is not…
Merge the base branch into open pull requests that conflict with it, one at a time with fix_github_pr_ci, and report the merges a person must decide. Use when asked to fix the merge conflicts on a repository's pull requests, and for scheduled conflict loops.
Computes a CI/CD metrics table from raw GitHub Actions records for one repository over the last 30 days, including failure rates and developer waiting time. Use for historical CI performance questions or the first-experience repository demo. For currently…
Present the available onboarding workflows and follow the selected skill. Use at interactive startup, for /demo, or when a user asks about OpenSRE capabilities. Direct workflow requests should load the matching specialist.
Read Yandex Cloud through its REST API. Applies to any question about VMs, metrics, logs, audit events, Kubernetes, managed databases, serverless, networking or any other Yandex Cloud resource. Never shell out to the `yc` CLI — it is not how this agent…
Use when the user asks OpenSRE to fix GitHub security and quality issues, Security and quality page findings, Code Quality standard findings, Dependabot alerts, code-scanning or CodeQL alerts, vulnerable dependencies, repo security issues, or to fix findings…
Default GitHub skill for the action agent. Use github_cli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shell_run/!gh. Run these with github_cli in…