Monitor CI/CD status for pull requests with error reporting. Triggers: "check CI", "CI status", "workflow status", "monitor CI", "检查CI", "CI状态", "查看构建".
/plugin marketplace add wuyuxiangX/yux-claude-hub/plugin install yux-linear-workflow@yux-claude-hubThis skill is limited to using the following tools:
Monitor GitHub Actions and other CI/CD checks for pull requests, with detailed error reporting and merge prompts.
This skill provides:
Triggered automatically after PR creation, or manually via:
gh pr view --json number,headRefName,state
If no PR found:
No pull request found for current branch.
Use /yux-linear-pr to create one.
gh pr checks <pr-number> --json name,state,conclusion,startedAt,completedAt,detailsUrl
Parse results:
| State | Conclusion | Display |
|---|---|---|
queued | - | ○ pending |
in_progress | - | ○ running |
completed | success | ✓ passed |
completed | failure | ✗ failed |
completed | skipped | ⊘ skipped |
completed | cancelled | ⊘ cancelled |
Running checks:
=== CI Status (Running) ===
PR #78: [LIN-456] Implement user authentication
├── ✓ lint (12s)
├── ✓ build (45s)
├── ○ test (running... 1m 30s)
├── ○ e2e (pending)
└── ○ deploy-preview (pending)
Progress: 2/5 checks passed
Estimated time remaining: ~5 minutes
All passed:
=== CI Status (Passed) ===
PR #78: [LIN-456] Implement user authentication
├── ✓ lint (12s)
├── ✓ build (45s)
├── ✓ test (2m 30s)
├── ✓ e2e (5m 12s)
└── ✓ deploy-preview (1m 8s)
All 5 checks passed!
Preview: https://preview-78.example.com
Ready to merge! Use /yux-linear-merge or say "merge".
When checks fail:
Identify failed check:
gh pr checks <pr-number> --json name,conclusion | jq '.[] | select(.conclusion == "failure")'
Get run ID:
gh pr checks <pr-number> --json name,conclusion,detailsUrl
Fetch error logs:
gh run view <run-id> --log-failed
Parse and display errors:
=== CI Status (Failed) ===
PR #78: [LIN-456] Implement user authentication
├── ✓ lint (12s)
├── ✓ build (45s)
├── ✗ test (failed)
├── ⊘ e2e (skipped)
└── ⊘ deploy-preview (skipped)
Failed: test
┌─────────────────────────────────────────────────────────────┐
│ Error Details │
├─────────────────────────────────────────────────────────────┤
│ │
│ FAIL src/auth/login.test.ts │
│ │
│ ● login › should return valid token │
│ │
│ expect(received).toBe(expected) │
│ │
│ Expected: "valid-token" │
│ Received: undefined │
│ │
│ at src/auth/login.test.ts:25:18 │
│ │
└─────────────────────────────────────────────────────────────┘
Suggestion:
The login function is not returning the token.
Check src/auth/login.ts around line 25.
Fix the issue and push to re-run CI.
For active monitoring:
Monitoring CI... (press Ctrl+C to stop)
[12:45:30] ○ test running (1m 15s)
[12:45:45] ○ test running (1m 30s)
[12:46:00] ✓ test passed (1m 45s)
[12:46:15] ○ e2e running (0s)
...
| Pattern | Cause | Suggestion |
|---|---|---|
npm ERR! | Dependency issue | Run npm install |
ENOENT | File not found | Check file paths |
TypeError | Type mismatch | Review type definitions |
timeout | Test too slow | Increase timeout or optimize |
ENOMEM | Out of memory | Reduce test parallelism |
Based on error content, provide actionable suggestions:
Test failure:
Suggestion: Test assertion failed.
- Review the test expectation
- Check if the implementation matches the test
- Run locally: npm test -- --grep "login"
Build failure:
Suggestion: Build compilation error.
- Check TypeScript errors
- Run locally: npm run build
- Fix import/export issues
Lint failure:
Suggestion: Code style violation.
- Run: npm run lint:fix
- Or manually fix the reported issues
| Symbol | Meaning |
|---|---|
| ✓ | Check passed |
| ✗ | Check failed |
| ○ | Running or pending |
| ⊘ | Skipped or cancelled |
All 5 checks passed! Ready to merge.
全部 5 项检查通过！准备合并。
全5件のチェックが完了しました！マージ可能です。
When CI fails, optionally update Linear issue:
mcp__linear__create_comment(
issueId: "LIN-456",
body: "CI failed: test\n\nError: ...\n\nWorking on fix."
)
When CI passes:
mcp__linear__create_comment(
issueId: "LIN-456",
body: "All CI checks passed! Ready for review and merge."
)
[14:32:15] CI Update
├── ✓ lint (passed)
├── ✓ build (passed)
├── ○ test (2m 15s elapsed)
└── ○ e2e (waiting)
Still running... next check in 15s
=== CI Complete ===
All checks passed in 8m 32s
├── ✓ lint 12s
├── ✓ build 45s
├── ✓ test 3m 20s
├── ✓ e2e 4m 5s
└── ✓ deploy 10s
Preview URL: https://preview.example.com
Merge now? [Y/n]
=== CI Failed ===
3 of 5 checks passed
├── ✓ lint
├── ✓ build
├── ✗ test ← Click for details
├── ⊘ e2e (skipped due to test failure)
└── ⊘ deploy (skipped)
See error details above. Fix and push to retry.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.