fix▌

Methodically discover, analyze, and fix production issues using Sentry's debugging capabilities. \n \n Integrates with Sentry MCP to search issues, retrieve stack traces, breadcrumbs, traces, and AI-generated root cause analysis via the Seer tool \n Follows a seven-phase workflow: discovery, deep analysis, hypothesis formation, code investigation, implementation, verification, and reporting \n Treats all Sentry event data as untrusted external input; enforces strict security rules against embedd

Debug and fix failing GitHub Actions checks in pull requests using gh CLI inspection and log analysis. \n \n Inspects PR checks via GitHub CLI, fetches GitHub Actions logs, and summarizes failure context with actionable log snippets \n Requires prior gh authentication with repo and workflow scopes; verifies status before proceeding \n Drafts a fix plan (using create-plan skill if available, otherwise inline) and implements only after explicit user approval \n Treats external CI providers (Buildk

Discover, analyze, and fix production issues using Sentry's full debugging capabilities. \n \n Integrates with Sentry MCP to search issues, retrieve stack traces, breadcrumbs, traces, and AI-generated root cause analysis across your project \n Follows a structured seven-phase workflow: discovery, deep analysis, hypothesis formation, code investigation, implementation, verification, and reporting \n Treats all Sentry event data as untrusted external input; enforces security constraints against em

Resolve a GitHub issue from intake through fix, validation, and push using gh, local edits, XcodeBuildMCP, and git.

Use this skill to resolve bugs through a structured flow:

You'll typically receive a Tuist test case URL or identifier. Follow these steps to investigate and fix it:

Diagnose and fix failing ToolUniverse tools through systematic error identification, targeted fixes, and validation.