什么是 DevOps Bridge？

DevOps Bridge 是一个复杂的集成层，旨在通过统一您的开发生态系统来消除上下文切换。作为 Openclaw Skills 的中心枢纽，它连接了 GitHub、CI/CD 流水线、Slack 和 Discord 等即时通讯平台，以及 Jira 或 Linear 等问题跟踪器。它将原始代码库数据转化为可操作的情报，确保您的团队在保持知情的同时不会被海量通知所淹没。

该技能专注于弥合工具之间的鸿沟——自动将 CI 失败链接到特定的 PR，在开发者首选的聊天应用中通知正确的人员，并使项目管理面板与实际的代码更改保持同步。无论您是在管理小型开源项目还是大型企业级单体仓库，DevOps Bridge 都能提供保持高速开发和维护仓库健康所需的自动化功能。

下载入口:https://github.com/openclaw/skills/tree/main/skills/ariktulcha/devops-bridge

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

DevOps Bridge 应用场景

• 直接将包含丰富上下文的 CI/CD 失败通知发送到 Slack 或 Discord 频道。
• 自动升级 PR 评审提醒，以减少合并等待时间。
• 在拉取请求合并时，自动同步 Jira 或 Linear 中的问题状态。
• 自动生成关于所有仓库活动的每日开发站会总结。
• 检测多个拉取请求中的不稳定测试和系统性构建失败。

1. 使用 gh CLI 与您的 GitHub 账户集成，坚控仓库事件、PR 状态和 CI/CD 结果。
2. 连接到配置好的即时通讯平台（如 Slack 或 Discord），提供格式化的、具备上下文感知的通知。
3. 坚控拉取请求的生命周期，跟踪评审者、批准情况和持续时间，以触发自动提醒。
4. 通过解析 PR 描述和分支名称中的问题密钥，与 Jira 或 Linear 等外部问题跟踪器同步。
5. 聚合跨工具数据，以按需或通过计划任务提供高级报告，如 CI 健康趋势和每日团队摘要。

DevOps Bridge 配置指南

要开始为 Openclaw Skills 使用此技能，请确保您已安装 GitHub CLI 并完成身份验证。

# 安装 GitHub CLI
brew install gh

# 登录您的 GitHub 账户
gh auth login

身份验证完成后，配置您的通知渠道和问题跟踪器：

1. 提供 Slack 或 Discord 的 Webhook URL 或机器人令牌。
2. （可选）配置 Linear 或 Jira API 访问权限以进行问题同步。
3. 运行交互式设置，将 GitHub 用户名映射到团队通讯账号。

DevOps Bridge 数据架构与分类体系

DevOps Bridge 组织其运行数据和元数据，以确保无缝的跨工具通信：

name: devops-bridge
description: >
  Unified developer operations bridge connecting GitHub, CI/CD (GitHub Actions), Slack, Discord, and
  issue trackers (Linear, Jira, GitHub Issues) into cross-tool automated workflows. Sends context-rich
  CI failure notifications to Slack with failing test details, tracks PR review lifecycle with escalating
  reminders, generates daily dev standup summaries, syncs issue status when PRs are merged, detects
  flaky tests, and monitors repository health. Use this skill for: PR review reminders, CI build alerts,
  "what happened in my repos", "any failing builds", "who needs a review", dev team standup summary,
  deploy notifications, repository monitoring, connecting GitHub to Slack, linking PRs to Jira/Linear
  tickets, code review tracking, merge conflict alerts, or any request to bridge development tools
  together. If the user mentions GitHub AND Slack (or any two dev tools) together, this skill connects them.
metadata:
  openclaw:
    emoji: "??"

DevOps Bridge

The missing link between your dev tools. This skill connects GitHub, CI/CD, Slack/Discord, and issue trackers into workflows that actually make sense — so you stop context-switching between 6 browser tabs.

Why This Exists

Developers already use separate skills for GitHub, Slack, etc. But nobody has built the bridge: when CI fails, automatically link it to the PR, notify the right Slack channel, and update the ticket. This skill is that bridge.

Core Capabilities

1. Smart Notifications

Transform noisy GitHub events into actionable, context-rich messages. Instead of "Build failed", deliver:

?? CI Failed — PR #142 "Add OAuth flow" by @alice
  └─ Test: auth.test.ts:47 — Expected 200, got 401
  └─ Last passing commit: abc1234 (2 hours ago)  
  └─ Linked issue: LINEAR-389 "Implement SSO"
  └─ Action: Reply "fix" to see the failing test, "logs" for full output

When sending notifications, always:

• Include the PR title and author, not just the number
• Link to the specific failing test or check, not just "CI failed"
• Mention the last known good commit for quick bisect context
• Cross-reference related issues/tickets if they exist
• Suggest a concrete next action

2. PR Review Management

Track pull request lifecycle across tools:

Review reminders:

• Scan open PRs daily and flag those waiting for review
• Escalate based on age: gentle reminder at 24h, stronger at 48h, urgent at 72h+
• Send reminders to the assigned reviewer via Slack/Discord DM or channel
• Format:

  ?? Review needed:
  ? PR #142 "Add OAuth flow" — waiting 3 days (assigned: @bob)
  ? PR #156 "Fix pagination" — waiting 1 day (assigned: @carol)
  

Review status sync:

• When a PR gets approved on GitHub, post to the team channel
• When changes are requested, notify the author directly
• When all checks pass + approved, prompt: "Ready to merge — want me to merge it?"

3. CI/CD Intelligence

Go beyond "pass/fail" with intelligent CI analysis:

• Failure grouping: if multiple PRs fail on the same test, flag it as a systemic issue rather than spamming individual notifications
• Flaky test detection: if a test fails intermittently across PRs, note it: "This test has failed 3 times this week across different PRs — likely flaky"
• Duration tracking: "This build took 45 min, up from the usual 20 min — something may be wrong"
• Auto-retry suggestion: for known flaky failures, suggest or trigger a re-run

4. Issue Tracker Sync

Keep issue trackers (Linear, Jira, GitHub Issues) in sync with actual development activity:

• When a PR references an issue (e.g., "Fixes #123"), update the issue status automatically
• When a PR is merged, move the linked issue to "Done" or "In Review"
• When CI fails on a PR linked to an issue, add a comment to the issue noting the blocker
• Surface orphaned PRs: "PR #167 doesn't reference any issue — should it?"

5. Daily Dev Standup

Generate a team-level development summary on demand or via cron:

????? Dev Standup — [Date]

Merged yesterday:
  ? PR #140 "Refactor auth module" by @alice → LINEAR-385 closed
  ? PR #143 "Update deps" by @bob

In review:
  ? PR #142 "Add OAuth flow" by @alice — 2 approvals, CI passing ?
  ? PR #156 "Fix pagination" by @carol — changes requested by @bob

Blocked:
  ? PR #158 "Migrate DB" by @dave — CI failing (migration timeout)
  ? Issue LINEAR-402 — no assignee, due tomorrow

CI Health: 87% pass rate (down from 94% last week)
  └─ Flaky: auth.test.ts (failed 4/10 runs)

Configuration

Required Tools

• gh CLI (GitHub) — for repo activity, PRs, issues, CI status
• At least one messaging channel configured (Slack, Discord, T@elegrimm)

Optional Tools

• Linear CLI or API — for Linear issue tracking
• Jira API — for Jira integration
• GitHub Issues — works out of the box with gh

Setup Flow

On first use, gather configuration interactively:

1. Which repos to monitor? Ask for a list or use "all repos I have push access to"
2. Where to send notifications? Slack channel, Discord channel, T@elegrimm, or all
3. How aggressive should reminders be? Options: gentle (72h), moderate (48h), aggressive (24h)
4. Include CI details? Some users want full logs, others just pass/fail
5. Who's on the team? Map GitHub usernames to Slack/Discord handles for @mentions

Store configuration in workspace memory for persistence.

Cron Setup

Suggest these default schedules (user can customize):

[
  {
    "name": "Morning dev digest",
    "schedule": "0 9 * * 1-5",
    "prompt": "Generate dev standup summary for my repos"
  },
  {
    "name": "PR review reminder",  
    "schedule": "0 14 * * 1-5",
    "prompt": "Check for PRs waiting for review and send reminders"
  },
  {
    "name": "End of day CI report",
    "schedule": "0 17 * * 1-5",
    "prompt": "Summarize today's CI/CD activity and flag any issues"
  }
]

Command Reference

Users can trigger specific actions with natural language:

Edge Cases

• Monorepo: if monitoring a monorepo, group notifications by directory/team, not just by PR
• Forks: when PRs come from forks, note this clearly (different trust level)
• Draft PRs: don't send review reminders for draft PRs unless user asks
• Stale PRs: if a PR has been open >7 days with no activity, suggest closing or rebasing
• Rate limits: GitHub API has rate limits. Batch requests and cache results within a session
• No messaging configured: if no Slack/Discord/T@elegrimm, output to the current conversation instead
• Multiple orgs: if user has repos across multiple GitHub orgs, handle them all but label clearly

Integration Pattern

This skill works best with other installed skills. When detected:

• github skill: defer raw GitHub operations to it, use devops-bridge for cross-tool logic
• slack skill: use it for message delivery, devops-bridge composes the messages
• daily-briefing-hub: feed dev activity data into the morning briefing's "Dev Activity" section