deployment-correlation

To correlate incidents with deployments, this Skill maps incidents to the most relevant deployments and commits within a defined time window. It fetches diffs and workflow runs to highlight suspicious commits that may have introduced the bug.

Yes, you can trace root causes across multiple repositories and branches. The Skill analyzes changes across repositories and PRs to assemble a complete narrative of what changed during multi-repo scenarios like hotfix deployments or feature rollouts.

You inspect GitHub commit diffs by running the included Python scripts to list recent commits, determine the deployment before the incident, and compare commits. The Skill uses a GitHub credential proxy to fetch workflow runs and diffs for deterministic investigation.

Yes, you need GitHub credentials to investigate CI/CD pipeline changes. The Skill relies on a GitHub credential proxy to securely fetch commits, diffs, and workflow runs for deterministic incident investigation.

The best way to identify which commit introduced a bug is to correlate the feature rollout deployment with recent code changes. The Skill maps the incident to the specific deployment and highlights suspicious commits and environment configurations that changed.