git-fix-pr
Analyze and fix failing PR checks. Use when asked to fix a PR, resolve red CI checks, auto-fix lint/test failures, or reproduce CI errors locally before pushing.
What this skill does
## When to Use This Skill | Use this skill when... | Use the alternative when... | |---|---| | Fixing failing CI checks on an existing PR (lint, type, test) | Use `git-pr-feedback` to address reviewer comments rather than CI failures | | Reproducing red GitHub Actions runs locally before pushing corrections | Use `gh-workflow-monitoring` to passively watch a run rather than fix it | | Auto-applying lint/format/type fixes and pushing them to the PR branch | Use `git-conflicts` when the failure is a merge conflict, not a check | | Diagnosing why a pull request is red after a push | Use `git-triage` to sweep many PRs at once instead of fixing one | ## Context - Repo: !`git remote get-url origin` - Current branch: !`git branch --show-current` - Git status: !`git status --porcelain=v2 --branch` - Staged changes: !`git diff --cached --numstat` - Unstaged changes: !`git diff --numstat` - Recent commits: !`git log --format='%h %s' --max-count=5` ## Parameters Parse these parameters from the command (all optional): - `$1`: PR number (if not provided, detect from current branch) - `--auto-fix`: Automatically apply fixes for common issues - `--push`: Push fixes to the branch after committing ## Your task Analyze and fix failing PR checks. ### Step 1: Determine PR 1. **Get PR number** from argument or detect from current branch 2. **Fetch PR status** using `gh pr checks <pr-number>` or mcp__github__pull_request_read ### Step 2: Analyze Failures 1. **Identify failing checks** from PR status 2. **Research error messages** in workflow logs 3. **Categorize failures**: - Linting errors - Type errors - Test failures - Build errors ### Step 3: Reproduce Locally 1. **Run tests locally** to reproduce issues 2. **Run linters** to check for style issues 3. **Run type checker** if applicable ### Step 4: Apply Fixes (if --auto-fix) Based on failure type: - **Linting errors**: Run appropriate linters/formatters ```bash # Python uv run ruff check --fix . uv run ruff format . # JavaScript/TypeScript npm run lint -- --fix ``` - **Type errors**: Fix type annotations or implementations - **Test failures**: Fix failing tests or implementation bugs ### Step 5: Commit and Push (if --push) 1. **Stage fixes**: `git add -u` 2. **Commit**: `git commit -m "fix: resolve CI failures"` 3. **Push**: `git push` ### Step 6: Verify 1. **Re-run checks** locally to verify fixes 2. **Monitor PR checks** after push ## Common Fix Patterns | Check Type | Common Fixes | |------------|--------------| | Linting | Run formatter, fix import order | | Types | Add type annotations, fix mismatches | | Tests | Fix assertions, update snapshots | | Build | Fix imports, resolve dependencies | ## See Also - **github-actions-inspection** skill for workflow analysis - **git-branch-pr-workflow** skill for PR patterns
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.