view-workflow
View GitHub Actions workflow runs and status
What this skill does
# View GitHub Actions Workflow
## Name
github:view-workflow - View GitHub Actions workflow runs and status
## Synopsis
```
/view-workflow [arguments]
```
## Description
View GitHub Actions workflow runs and status
## Implementation
View the status of GitHub Actions workflow runs for a repository or pull request.
## Usage
```
/view-workflow [owner/repo] [run-id or pr-number]
```
This command displays comprehensive workflow and job information.
## What This Command Does
1. Fetches workflow run data for a repository or PR
2. Retrieves all jobs in the workflow using `list_workflow_runs`
3. Displays:
- Workflow status and duration
- Individual job statuses
- Failed job logs (if any)
- Job durations and timestamps
- Workflow trigger information
## Prerequisites
- GitHub MCP server must be installed and configured
- You must have access to the repository
- OAuth authentication must be completed
## Example Interaction
### View Latest Workflow Runs
```
User: /view-workflow my-org/my-repo
Claude: Fetching workflow runs for my-org/my-repo...
## Recent Workflow Runs
### Run #1234 - CI Pipeline
**Status**: Running
**Branch**: feature/user-auth
**Triggered by**: Push by @johndoe
**Started**: 3 minutes ago
Jobs:
- build: Passed (1m 23s)
- test: Running (2m 15s elapsed)
- lint: Pending
- deploy: Pending
### Run #1233 - CI Pipeline
**Status**: Success
**Branch**: main
**Duration**: 4m 32s
**Completed**: 1 hour ago
All jobs passed.
```
### View Failed Workflow
```
User: /view-workflow my-org/my-repo 1232
Claude: Fetching workflow run #1232...
## Workflow Run #1232 - CI Pipeline
**Status**: Failed
**Branch**: feature/new-feature
**Duration**: 2m 45s
### Jobs by Status
#### Failed
- test (2m 15s)
**Error**: Test suite failed with 3 failures
```
FAIL src/auth.test.ts
Authentication API
POST /login
should return JWT token
Expected: 200
Received: 500
```
#### Passed
- build (1m 18s)
- lint (24s)
#### Skipped
- deploy (skipped due to test failure)
### Recommendations
1. Check database connection in test environment
2. Review test timeout settings
3. Re-run workflow after fixes
```
## Arguments
- `owner/repo` (required): Repository in owner/repo format
- `run-id` (optional): Specific workflow run ID to view
- `pr-number` (optional): View workflows for a specific PR
## Tips
- Monitor workflows during active development
- Investigate failed jobs immediately
- Compare run times to identify bottlenecks
- Check if tests are flaky or consistently failing
- Review job logs for specific error messages
- Use workflow status to determine PR readiness
## Common Issues
### Failed Tests
- Review test logs for specific failures
- Check if tests pass locally
- Verify test environment configuration
- Look for flaky tests
### Build Errors
- Check for missing dependencies
- Verify build configuration
- Look for syntax or compilation errors
### Timeout Issues
- Increase timeout values if needed
- Optimize slow tests or builds
- Check for infinite loops
## Related Commands
- `/review-pr`: Full PR review including workflow status
- `/create-pr`: Create PR that will trigger workflows
- `/create-issue`: Create issue for workflow failures
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.