Skip to content
Skills Library
Programming · Tool integration

dev-tool-integrations

/dev-tool-integrations

Connects a startup's dev tools: GitHub and Vercel notifications into Slack, Linear issues linked to branches and PRs, Sentry alerts into Slack, with step-by-step setup and a connectivity map. Use when the user asks to connect GitHub, Slack, Linear, Jira, Sentry or Vercel, set up PR, deploy or error notifications, or says their tools do not talk to each other. Not for installing Sentry itself (use monitoring-setup).

Repository
skills ↗
Licence
Apache-2.0
Last repository change
11.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
3
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Connects a startup's dev tools: GitHub and Vercel notifications into Slack, Linear issues linked to branches and PRs, Sentry alerts into Slack, with step-by-step setup and a connectivity map. Use when the user asks to connect GitHub, Slack, Linear, Jira, Sentry or Vercel, set up PR, deploy or error notifications, or says their tools do not talk to each other. Not for installing Sentry itself (use monitoring-setup).

Original author description

Connects a startup's dev tools: GitHub and Vercel notifications into Slack, Linear issues linked to branches and PRs, Sentry alerts into Slack, with step-by-step setup and a connectivity map. Use when the user asks to connect GitHub, Slack, Linear, Jira, Sentry or Vercel, set up PR, deploy or error notifications, or says their tools do not talk to each other. Not for installing Sentry itself (use monitoring-setup).

How it works

  1. How It Works
  2. Step-by-Step Procedure
  3. Output Format
Original SKILL.md headings · 151 lines, 606 words
SKILL.md preview
---
name: dev-tool-integrations
description: >-
  Connects a startup's dev tools: GitHub and Vercel notifications into Slack, Linear issues linked
  to branches and PRs, Sentry alerts into Slack, with step-by-step setup and a connectivity map.
  Use when the user asks to connect GitHub, Slack, Linear, Jira, Sentry or Vercel, set up PR,
  deploy or error notifications, or says their tools do not talk to each other. Not for installing
  Sentry itself (use monitoring-setup).
---

# Integration Linker

Detects which development tools are in use and connects them together with step-by-step procedures.

## How It Works

1. Run detection commands to find which tools are configured
2. Identify missing high-value connections
3. Provide step-by-step setup for each recommended integration
4. Verify connections work

## Step-by-Step Procedure

### Step 1: Detect Current Tools

Detection prints filenames only, especially for .env files. Never expose token, webhook or other secret values.
```bash
# Detect Slack
grep -rl "SLACK_\|slack-sdk\|@slack/\|slack-webhook" --include="*.ts" --include="*.js" --include="*.py" --include="*.env*" . 2>/dev/null | head -5

# Detect Linear
grep -rl "LINEAR_\|linear-sdk\|@linear/sdk" --include="*.ts" --include="*.js" --include="*.env*" . 2>/dev/null | head -5

# Detect project management (Jira, Asana, Notion)
grep -rl "JIRA_\|ASANA_\|NOTION_\|jira\|asana\|@notionhq" --include="*.ts" --include="*.js" --include="*.env*" . 2>/dev/null | head -5

# Detect CI/CD (already linked?)
ls .github/workflows/ 2>/dev/null

# Detect error tracking (Sentry, PostHog)
grep -rl "SENTRY_DSN\|POSTHOG_\|sentry\|posthog" --include="*.ts" --include="*.js" --include="*.env*" . 2>/dev/null | head -5

# Detect hosting platform
ls vercel.json railway.toml fly.toml render.yaml 2>/dev/null
```

### Step 2: Set Up GitHub → Slack Notifications
**Source:** [GitHub Slack integration](https://github.com/integrations/slack)

1. In Slack: Go to your workspace → Apps → Search "GitHub" → Install
2. In a Slack channel, type: `/github subscribe owner/repo`
3. This enables: issue/PR notifications, deployment status, CI results

To customize notifications:
```bash
# In Slack channel:
/github subscribe owner/repo pulls commits releases deployments
/github unsubscribe owner/repo issues
```

For webhook-based alerts (more control):
```yaml
# .github/workflows/notify-slack.yml
name: Slack Notification
on:
  push:
    branches: [main]
  pull_request:
    types: [opened, closed]
permissions:
  contents: read
jobs:
  notify:
    if: github.event_name == 'push' || github.event.action == 'opened' || (github.event.action == 'closed' && github.event.pull_request.merged == true)
    runs-on: ubuntu-latest
    steps:
      - name: Encode notification as JSON
        run: |
          python3 - <<'PYTHON'
          import json, os
          from pathlib import Path
          event = json.loads(Path(os.environ['GITHUB_EVENT_PATH']).read_text())
          title = event.get('pull_request', {}).get('title') or (event.get('head_commit') or {}).get('message', '')
          Path('payload.json').write_text(json.dumps({'text': os.environ['GITHUB_EVENT_NAME'] + ': ' + title}))
          PYTHON
      - name: Send notification
        env:
          SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}
        run: |
          if [ -n "$SLACK_WEBHOOK_URL" ]; then
            curl --fail --silent --show-error -H 'Content-type: application/json' --data-binary @payload.json "$SLACK_WEBHOOK_URL"
          else
            echo "Notification skipped: webhook secret unavailable for this event."
          fi
```

### Step 3: Set Up Linear → GitHub Sync
**Source:** [Linear GitHub integration docs](https://linear.app/integrations/github)

1. In Linear: Settings → Integrations → GitHub → Connect
2. Select which repos to link
3. Enable PR linking and commit linking

**Branch naming convention** (auto-links PRs to issues):
```bash
# Use Linear issue ID in branch name:
git checkout -b feat/LIN-123-add-user-auth

# Or in PR title:
# "LIN-123: Add user authentication"
```

**Magic words in PR description** (alternative linking):
```
Fixes LIN-123
Closes LIN-123
Resolves LIN-123
```

**Workflow automations** (per-team settings):
- PR opened → Issue moves to "In Progress"
- PR merged → Issue moves to "Done"
- PR closed → Issue moves back to "Todo"

### Step 4: Set Up Sentry → Slack Alerts
**Source:** [Sentry Integrations](https://sentry.io/integrations/)

1. In Sentry: Settings → Integrations → Slack → Install
2. Configure alert rules: Settings → Alerts → Create Alert
3. Set conditions: "When an issue is first seen" → "Send Slack notification to #engineering"

### Step 5: Set Up Vercel → Slack Deploy Notifications
1. In Vercel dashboard: Settings → Integrations → Slack → Install
2. Select project and channel
3. Enables: deploy started, deploy succeeded, deploy failed notifications

## Output Format

```markdown
## 🔗 Integration Status

### Currently Connected
- {Tool A} ↔ {Tool B}: {what's linked}

### Recommended Connections
1. **{Tool A} → {Tool B}** — Why: {one sentence value prop}
   Setup time: ~{X} minutes
   Steps: {numbered list}

### Connectivity Map
GitHub ──→ Slack (PR notifications)
  │
  └──→ Linear (auto-link issues)
  │
  └──→ Vercel (auto-deploy)
         │
         └──→ Slack (deploy notifications)
Sentry ──→ Slack (error alerts)
```

Versions

The database has no other skills named dev-tool-integrations.

Database snapshot: 13.11.2026 · package version 5c0b3bff8453 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100integration-linker
    Detects and connects development tools — Slack with GitHub, Linear with Git, error tracking with notifications. Provides step-by-step setup procedures for each integration. Use when the user asks to "connect tools", "link Slack", "set up notifications", "integrate Linear", or…
  • 95sentry-sdk-setup
    Set up Sentry in any language or framework. Detects the user's platform and loads the right SDK skill. Use when asked to add Sentry, install an SDK, or set up error monitoring in a project.
  • 95sentry-code-review
    Analyze and resolve Sentry comments on GitHub Pull Requests. Use this when asked to review or fix issues identified by Sentry in PR comments. Can review specific PRs by number or automatically find recent PRs with Sentry feedback.
  • 100fix-sentry-issues
    使用 Sentry MCP 发现、分类并根因修复生产问题。用于修复 Sentry 问题、分类生产错误、排查错误尖峰或清理 Sentry 噪声。需要 Sentry MCP 服务。
  • 95sentry-alerts-issues
    Use when configuring Sentry alerts, managing issues, or setting up notifications. Covers alert rules, issue triage, and integrations.
  • 90slack-agent
    Use when building Slack agents/bots with eve (Vercel's filesystem-first agent framework), @vercel/connect, or eve/channels/slack. Covers defineAgent/defineTool patterns, Vercel Connect credential brokering, Slack channel setup, testing requirements, and quality standards.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.