Dev Tool Integrations

---
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)
```