Correlate GitHub incident time windows with PRs, workflow runs, releases, and deployments.
npx skills add https://github.com/tsuga-dev/agent-plugins --skill gh-tsuga-dev
Please help me install this Agent Skill. Skill: gh Source: https://github.com/tsuga-dev/agent-plugins/tree/main/plugins/tsuga/skills/gh Command: npx skills add https://github.com/tsuga-dev/agent-plugins --skill gh-tsuga-dev
This Skill helps you determine what changed and what actually shipped during an incident window by inspecting GitHub workflow runs, PRs, releases, and deployments.
Ask the AI to correlate your incident time window (start/end) with the GitHub repo’s merged PRs and the deployed workflow runs for the affected environments using gh.
High-intent search queries and answers about installing and using this skill.
Incident triage with GitHub involves inspecting merged PRs, workflow runs, releases, and deployment statuses within a specific time window to determine what changed. It distinguishes merged code from actual production deployments using read-only GitHub CLI commands.
A merged GitHub pull request may not reach production if the workflow run failed or the deployment status per environment remains pending. Deployment verification requires checking workflow run outcomes and environment-specific deployment statuses rather than relying on CI pass or fail colors alone.
Verify deployment status per environment by executing read-only GitHub CLI inspection commands to validate workflow runs and deployment outcomes for the affected environments. This provides citations like run URLs and commit SHAs to confirm whether the expected deploy actually occurred.
Yes, investigating GitHub workflow runs and release tracking requires an authenticated GH_TOKEN environment variable. The GitHub CLI uses this token to execute read-only inspection commands for PRs, workflow runs, and deployment statuses.
The best way to perform commit-level impact analysis is to correlate a specific commit SHA with merged PRs, workflow executions, and deployment outcomes during the incident window. This evidence-first approach provides verifiable citations like run URLs and release tags.
Yes, this approach supports release verification across multiple environments by validating per-environment deployment and workflow run statuses. It tracks release tags and run outcomes to confirm delivery in repositories where deployments are managed independently.
fxAutomate GitHub PR operations with gh CLI and GitHub API.
rajyeole6Perform forensic triage and incident response on Windows and Linux systems.
williamzujkowskiInstrument services with Prometheus-compatible metrics and Grafana dashboards.
NagyViktTriage GitHub repositories, pull requests, and issues with local git operations.
