pr-health
Check PR health status (conflicts, CI, approval) and get actionable next steps
What this skill does
# PR Health Skill Check the health of a pull request including merge conflicts, CI status, and approval status. ## Commands ### Check PR Health ```bash # Check PR for current branch toolkit pr health # Check specific PR toolkit pr health 123 # Output as JSON toolkit pr health --json # Specify repository toolkit pr health --repo owner/repo ``` ### Get Workflow Logs ```bash # Get all logs for a run toolkit pr logs <run-id> # Get only failed job logs toolkit pr logs <run-id> --failed-only # Get logs for specific job toolkit pr logs <run-id> --job "build" ``` ### Detect PR ```bash # Find PR for current branch toolkit pr detect # Output as JSON toolkit pr detect --json ``` ## Output Format The health command outputs a structured report: ``` ## PR Health Report: #123 **URL:** https://github.com/owner/repo/pull/123 ### Status: UNHEALTHY (2 issues) ### Merge Conflicts: UNHEALTHY - Branch has merge conflicts with base - Conflicting file: src/lib/parser.ts To investigate: \`\`\`bash git fetch origin main && git merge origin/main \`\`\` ### CI Status: FAILED - Job "test" - FAILED - Run ID: 12345678 To investigate: \`\`\`bash toolkit pr logs 12345678 --failed-only \`\`\` ### Approval: APPROVED - claude-code-review[bot]: APPROVED ### Next Steps 1. Resolve merge conflicts 2. Fix CI failures ``` ## Status Values - **HEALTHY**: No issues - **UNHEALTHY**: Issues need to be addressed - **PENDING**: Waiting for something (CI running, reviews needed) ## Troubleshooting ### "No PR found for current branch" Create a PR first or specify a PR number: ```bash gh pr create # or toolkit pr health 123 ``` ### CI logs are empty The workflow run may not have generated logs yet. Wait for the run to complete. ### Merge conflict detection is inaccurate Ensure you have fetched the latest from origin: ```bash git fetch origin main ```
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.