devops-bridgeUnified developer operations bridge connecting GitHub, CI/CD (GitHub Actions), Slack, Discord, and issue trackers (Linear, Jira, GitHub Issues) into cross-to...
Install via ClawdBot CLI:
clawdbot install ariktulcha/devops-bridgeThe 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.
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.
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 outputWhen sending notifications, always:
Track pull request lifecycle across tools:
Review reminders:
š Review needed:
ā¢ PR #142 "Add OAuth flow" ā waiting 3 days (assigned: @bob)
ā¢ PR #156 "Fix pagination" ā waiting 1 day (assigned: @carol)Review status sync:
Go beyond "pass/fail" with intelligent CI analysis:
Keep issue trackers (Linear, Jira, GitHub Issues) in sync with actual development activity:
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)gh CLI (GitHub) ā for repo activity, PRs, issues, CI statusghOn first use, gather configuration interactively:
Store configuration in workspace memory for persistence.
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"
}
]Users can trigger specific actions with natural language:
| User says | Action |
|-----------|--------|
| "What's happening in my repos?" | Full activity summary across all monitored repos |
| "Any failing builds?" | CI status check with details on failures |
| "Who needs a review?" | List PRs awaiting review with age and assignee |
| "Standup" | Generate daily dev standup summary |
| "Notify #dev-team about PR 142" | Send a formatted notification about a specific PR |
| "Link PR 142 to LINEAR-389" | Create cross-reference between PR and issue |
| "Set up CI alerts for repo X" | Configure monitoring for a specific repository |
| "Merge PR 142" | Merge if all checks pass and approved; warn if not |
This skill works best with other installed skills. When detected:
Generated Mar 1, 2026
A fast-moving startup uses GitHub for code, Linear for issue tracking, and Slack for team communication. This skill automates CI failure notifications with test details to Slack, syncs Linear ticket status when PRs are merged, and sends daily standup summaries to keep the team aligned without manual updates.
A large corporation manages multiple repositories with GitHub, uses Jira for project management, and relies on Slack for internal alerts. The skill bridges these tools by sending PR review reminders to assigned reviewers, detecting flaky tests across builds, and generating health reports to monitor repository performance and reduce downtime.
An open source project on GitHub uses Discord for community discussions and GitHub Issues for bug tracking. This skill connects these platforms by notifying Discord channels of CI failures with actionable details, tracking PR review lifecycles to prevent bottlenecks, and syncing issue status automatically when contributions are merged.
A small agency handles client projects using GitHub for version control, Slack for client updates, and various issue trackers like Jira or Linear. The skill automates deploy notifications to clients, links PRs to tickets for transparency, and provides daily summaries of development activity to streamline reporting and improve client communication.
A university or coding bootcamp uses GitHub for student projects, Slack for instructor coordination, and GitHub Issues for assignment tracking. This skill bridges tools by sending alerts for merge conflicts, generating standup summaries for class progress, and monitoring repository health to identify common student issues and improve learning outcomes.
Offer tiered monthly subscriptions based on features like number of repositories, integrations (e.g., Jira, Linear), and notification volume. Revenue comes from small teams to large enterprises, with pricing scaled to usage and support levels.
Provide a free version with basic notifications and limited integrations, then charge for advanced features like flaky test detection, custom workflows, and priority support. Revenue is generated from upgrades as teams grow and need more automation.
Sell annual licenses to large organizations with custom integrations, on-premise deployment options, and dedicated support. Revenue includes upfront fees and ongoing maintenance contracts, targeting industries with strict compliance needs.
š¬ Integration Tip
Start by configuring GitHub and one messaging channel like Slack, then gradually add issue trackers to avoid overwhelming setup; use the interactive configuration flow to tailor reminders and notifications to your team's workflow.
Automatically update Clawdbot and all installed skills once daily. Runs via cron, checks for updates, applies them, and messages the user with a summary of what changed.
Full desktop computer use for headless Linux servers. Xvfb + XFCE virtual desktop with xdotool automation. 17 actions (click, type, scroll, screenshot, drag,...
Essential Docker commands and workflows for container management, image operations, and debugging.
Tool discovery and shell one-liner reference for sysadmin, DevOps, and security tasks. AUTO-CONSULT this skill when the user is: troubleshooting network issues, debugging processes, analyzing logs, working with SSL/TLS, managing DNS, testing HTTP endpoints, auditing security, working with containers, writing shell scripts, or asks 'what tool should I use for X'. Source: github.com/trimstray/the-book-of-secret-knowledge
Deploy applications and manage projects with complete CLI reference. Commands for deployments, projects, domains, environment variables, and live documentation access.
Monitor topics of interest and proactively alert when important developments occur. Use when user wants automated monitoring of specific subjects (e.g., product releases, price changes, news topics, technology updates). Supports scheduled web searches, AI-powered importance scoring, smart alerts vs weekly digests, and memory-aware contextual summaries.