OpenClaw for Developers: The Ultimate Productivity Setup

openclaw skills install @<publisher>/github-bridge
openclaw skills install @<publisher>/linear-sync
openclaw skills install @<publisher>/cicd-monitor
openclaw skills install @<publisher>/nextjs-docs

openclaw skills install @<publisher>/flaw0-scanner
openclaw skills install @<publisher>/workflow-builder

{
  skills: {
    entries: {
      "github-bridge": {
        enabled: true,
        apiKey: { source: "env", provider: "default", id: "GITHUB_TOKEN" },
        config: {
          auto_review: {
            enabled: true,
            trigger: "on_push", // skill-owned field, not an OpenClaw config key
            repos: ["your-org/main-repo", "your-org/api-service"],
            review_model: "claude-sonnet-4-6-20260217",
            review_standards: {
              code_quality: {
                enabled: true,
                check_naming: true,
                check_complexity: true,
                max_function_length: 50,
                check_duplication: true,
              },
              security: {
                enabled: true,
                check_sql_injection: true,
                check_xss: true,
                check_secrets: true,
                check_dependencies: true,
              },
              performance: {
                enabled: true,
                check_n_plus_one: true,
                check_memory_leaks: true,
                check_async_patterns: true,
              },
              testing: {
                enabled: true,
                require_tests: true,
                min_coverage_suggestion: true,
              },
            },
            review_format: {
              summary: true,
              inline_comments: true,
              severity_labels: true,
              approval_recommendation: true,
            },
            ignore_patterns: ["*.lock", "*.generated.*", "package-lock.json", "yarn.lock"],
          },
        },
      },
    },
  },
}

## Agent Review Summary
**Overall Assessment:** Mostly good, 2 issues to address before merge.
### Issues Found
#### 🔴 Security (Critical)
- `src/api/users.ts:42` — SQL query uses string interpolation instead of
  parameterized query. This is a SQL injection vulnerability.
#### 🟡 Performance (Warning)
- `src/services/orders.ts:78-92` — This loop makes a database query on
  each iteration. Consider batch-fetching orders to avoid N+1 query.
#### 🟢 Code Quality (Suggestion)
- `src/utils/helpers.ts:15` — Function `processData` is 67 lines long.
  Consider breaking it into smaller focused functions.
### What Looks Good
- Clean separation of concerns in the new middleware
- Good error handling with typed error responses
- Tests cover the happy path and two edge cases
**Recommendation:** Request changes (address the SQL injection issue)

{
  skills: {
    entries: {
      "github-bridge": {
        enabled: true,
        config: {
          issue_management: {
            auto_label: true,
            label_model: "claude-haiku-4-20260210",
            auto_assign: {
              enabled: true,
              rules: {
                frontend: "frontend-team-lead",
                backend: "backend-team-lead",
                security: "security-team-lead",
              },
            },
            triage_new_issues: true,
            stale_issue_check: {
              enabled: true,
              days_until_stale: 30,
              comment_on_stale: true,
            },
          },
        },
      },
    },
  },
}

You: "Find all places where we use the deprecated `fetchUser` function"
Agent: "Found 14 occurrences across 3 repos:
  - org/main-app: 8 occurrences (src/services/auth.ts, src/api/users.ts, ...)
  - org/api-service: 4 occurrences (src/handlers/user.ts, ...)
  - org/admin-panel: 2 occurrences (src/lib/api.ts, ...)
  Shall I create a tracking issue for the migration?"

{
  skills: {
    entries: {
      "linear-sync": {
        enabled: true,
        apiKey: { source: "env", provider: "default", id: "LINEAR_API_KEY" },
        config: {
          team_id: "your-team-id",
          sprint_planning: {
            enabled: true,
            suggest_priorities: true,
            estimate_complexity: true,
            balance_workload: true,
            carry_over_incomplete: true,
          },
        },
      },
    },
  },
}

You: "Help me plan next sprint. What didn't get done this sprint,
     and what's the highest priority in the backlog?"
Agent: "Current sprint ends Friday. Here's the status:
  Completed: 14 issues (42 points)
  In Progress: 3 issues (8 points) — likely to finish
  Not Started: 2 issues (5 points) — should carry over
  For next sprint, here are the top priorities from the backlog:
  1. [HIGH] Payment processing refactor (8 pts) — blocked 3 other issues
  2. [HIGH] Fix authentication timeout bug (3 pts) — 12 customer reports
  3. [MED] Add pagination to user list API (5 pts) — performance bottleneck
  4. [MED] Update onboarding flow (5 pts) — design approved last week
  5. [LOW] Migrate to new logging library (3 pts) — tech debt
  Based on the team's velocity of ~45 points, I'd suggest taking all 5
  plus the 2 carry-overs for a total of 29 points, leaving room for
  unplanned work."

{
  skills: {
    entries: {
      "linear-sync": {
        enabled: true,
        config: {
          auto_standup: {
            enabled: true,
            schedule: "0 9 * * 1-5",
            channel: "telegram",
            model: "claude-sonnet-4-6-20260217",
            data_sources: {
              git_commits: {
                enabled: true,
                repos: ["org/main-repo", "org/api-service"],
                lookback_hours: 24,
              },
              linear_updates: {
                enabled: true,
                include_status_changes: true,
                include_comments: true,
              },
              pr_activity: {
                enabled: true,
                include_reviews: true,
                include_merges: true,
              },
            },
            format: {
              sections: ["yesterday", "today", "blockers"],
              tone: "concise and factual",
              max_items_per_section: 5,
            },
          },
        },
      },
    },
  },
}

## Daily Standup — Tuesday, Feb 24
### Yesterday
- Merged PR #342: Add rate limiting to public API endpoints
- Reviewed and approved PR #339: Database migration for user preferences
- Moved LIN-456 (payment refactor) to In Review
- Fixed flaky test in CI (3 commits to test/integration/payments.test.ts)
### Today
- LIN-456: Payment refactor — address review comments, target merge
- LIN-461: Start authentication timeout investigation (12 customer reports)
- PR #339: Follow up on migration — verify staging deployment
### Blockers
- None currently. Waiting on design review for LIN-470 (onboarding flow)
  but it's not blocking this sprint's work.

You: "Prioritize the backlog for the API team based on customer impact,
     technical debt, and blocking relationships."
Agent: "Here's the prioritized backlog:
  Priority 1 (Do First):
  - LIN-456: Payment processing refactor — blocks LIN-458, LIN-460, LIN-462
  - LIN-461: Auth timeout bug — 12 customer reports, revenue impact
  Priority 2 (Do Next):
  - LIN-470: Onboarding flow update — design approved, improves conversion
  - LIN-473: Pagination for user list — performance degradation at scale
  Priority 3 (Backlog):
  - LIN-480: Logging library migration — tech debt, no customer impact
  - LIN-482: Add dark mode to admin panel — nice to have
  Reasoning: I prioritized based on blocking relationships first (LIN-456
  unblocks 3 issues), then customer-reported bugs, then customer-facing
  improvements, then internal improvements."

{
  agents: {
    entries: {
      "code-reviewer": {
        name: "Code Reviewer",
        workspace: "~/.openclaw/workspace-code-reviewer",
        model: "anthropic/claude-sonnet-4-6",
        skills: ["github-bridge", "flaw0-scanner"],
      },
    },
  },
}

# Code Reviewer Agent
You are a senior software engineer conducting code reviews. Your reviews are:
- Thorough but not nitpicky. Focus on issues that matter.
- Security-first. Always check for vulnerabilities before anything else.
- Constructive. Every criticism comes with a suggested improvement.
- Contextual. Understand the PR's purpose before reviewing details.
## Review Checklist
1. Security: injection, authentication, authorization, data exposure
2. Performance: queries, loops, memory, caching
3. Correctness: edge cases, error handling, race conditions
4. Maintainability: naming, complexity, documentation
5. Testing: coverage, edge cases, test quality
## What to Skip
- Style nitpicks that a formatter should handle
- Personal preferences that don't affect quality
- Changes outside the PR's scope (file a separate issue instead)

{
  skills: {
    entries: {
      "github-bridge": {
        enabled: true,
        config: {
          auto_review: {
            repo_overrides: {
              "org/main-repo": {
                review_model: "claude-opus-4-6-20260217",
                review_standards: ["security", "performance", "testing"],
                require_tests: true,
              },
              "org/docs-site": {
                review_model: "claude-haiku-4-20260210",
                review_standards: ["spelling", "links", "formatting"],
                require_tests: false,
              },
              "org/prototype": {
                review_model: "claude-haiku-4-20260210",
                review_standards: ["security"],
                require_tests: false,
              },
            },
          },
        },
      },
    },
  },
}

You: "I'm migrating from Next.js 14 to 16. What are the breaking changes
     I need to handle?"
Agent: [Detailed list of breaking changes with code migration examples]

You: "What's the best way to handle authentication in Next.js 16 App Router
     with server components?"
Agent: [Explanation with code examples for middleware-based auth, server
       component checks, and client component patterns]

You: "Review my app/page.tsx for Next.js anti-patterns."
Agent: [Analysis of the file with specific recommendations]

{
  skills: {
    entries: {
      "nextjs-docs": {
        enabled: true,
        config: {
          version: "16",
          include_examples: true,
          migration_helpers: true,
          best_practice_checks: true,
          project_path: "/Users/you/projects/my-nextjs-app",
          watch_for_updates: true,
          update_channel: "stable",
        },
      },
    },
  },
}

{
  skills: {
    entries: {
      "cicd-monitor": {
        enabled: true,
        config: {
          providers: {
            github_actions: {
              token: "ghp_your_token",
              repos: ["org/main-repo", "org/api-service"],
              watched_workflows: ["ci.yml", "deploy.yml", "test.yml"],
            },
          },
          alerts: {
            on_failure: {
              enabled: true,
              channel: "telegram",
              include_logs: true,
              log_lines: 50,
              mention_author: true,
            },
            on_success_after_failure: {
              enabled: true,
              channel: "telegram",
              message: "Pipeline recovered",
            },
            on_long_running: {
              enabled: true,
              threshold_minutes: 30,
              channel: "telegram",
            },
          },
          auto_create_issue: {
            enabled: true,
            tracker: "linear",
            label: "ci-failure",
            assign_to_author: true,
          },
          daily_summary: {
            enabled: true,
            schedule: "0 17 * * 1-5",
            channel: "telegram",
          },
        },
      },
    },
  },
}

🔴 CI Failure: org/main-repo — ci.yml
**Branch:** feature/add-rate-limiting
**Author:** @yourname
**Commit:** abc1234 "Add rate limiting middleware"
**Failed Job:** integration-tests
**Duration:** 4m 32s
**Relevant Logs (last 30 lines):**
```
FAIL src/test/integration/rate-limit.test.ts
  ● Rate Limiting › should return 429 after 100 requests
    Expected: 429
    Received: 200
    at Object.<anonymous> (src/test/integration/rate-limit.test.ts:45:27)
Test Suites: 1 failed, 24 passed
Tests: 1 failed, 156 passed
```
**Auto-created Linear issue:** LIN-501
**Quick link:** [View workflow run](https://github.com/org/main-repo/actions/runs/123)

## Standup Format
When generating standups:
- Keep each item to one line. No lengthy descriptions.
- Link to PRs and issues when referencing them.
- For "Today" section, pull from Linear issues assigned to me that are
  In Progress or marked as next up.
- Only include blockers if they are genuine blockers. Do not fabricate
  blockers to fill the section. If there are no blockers, say "None."
- Total standup should be under 15 lines.

{
  skills: {
    entries: {
      "github-bridge": {
        enabled: true,
        config: {
          deployment: {
            staging: {
              branch: "staging",
              auto_deploy: true,
              trigger: "merge_to_staging", // skill-owned field, not an OpenClaw config key
              checks: ["ci_pass", "no_critical_issues"],
            },
            production: {
              branch: "main",
              auto_deploy: false,
              require_approval: true,
              approval_channel: "telegram",
              checks: [
                "ci_pass",
                "staging_healthy_for_hours",
                "no_critical_issues",
                "no_active_incidents",
              ],
              staging_healthy_hours: 4,
              rollback_on_failure: true,
              notification_channel: "telegram",
            },
          },
        },
      },
    },
  },
}

{
  agents: {
    defaults: {
      model: { primary: "anthropic/claude-sonnet-4-6" },
      heartbeat: {
        every: "15m",
        activeHours: { start: "08:00", end: "22:00" },
        // model: "<provider>/<model>" runs the heartbeat on a cheaper route
      },
      userTimezone: "America/New_York",
    },
  },
  channels: {
    telegram: {
      enabled: true,
      botToken: "your-telegram-bot-token",
      dmPolicy: "allowlist",
      allowFrom: ["tg:123456789"],
    },
  },
  skills: {
    entries: {
      "github-bridge": {
        enabled: true,
        apiKey: { source: "env", provider: "default", id: "GITHUB_TOKEN" },
        config: {
          default_org: "your-org",
          auto_review: { enabled: true, on_push: true },
        },
      },
      "linear-sync": {
        enabled: true,
        apiKey: { source: "env", provider: "default", id: "LINEAR_API_KEY" },
        config: { team_id: "your-team-id" },
      },
      "cicd-monitor": {
        enabled: true,
        config: {
          providers: {
            github_actions: { repos: ["org/main-repo"] },
          },
          alert_on: ["failure"],
          alert_channel: "telegram",
        },
      },
      "nextjs-docs": {
        enabled: true,
        config: { version: "16", project_path: "/path/to/your/project" },
      },
    },
  },
  cron: {
    enabled: true,
  },
}

openclaw cron add "0 8 * * 1-5" "Morning PR digest: List all open PRs across watched repos. For each PR, show title, author, age, review status, and CI status. Highlight PRs that need my review." --name "Morning PR digest" --announce --channel telegram --to "-1001234567890"
openclaw cron add "0 9 * * 1-5" "Generate daily standup from git commits (last 24h), Linear status changes, and PR activity. Format as Yesterday/Today/Blockers." --name "Daily standup" --announce --channel telegram --to "-1001234567890"
openclaw cron add "0 18 * * 1-5" "End-of-day commit summary: List all commits I made today across all repos. Group by repo. Include total lines changed and PRs opened/merged." --name "End of day" --announce --channel telegram --to "-1001234567890"
openclaw cron add "0 */3 * * 1-5" "CI health check: Report on pipeline status across all watched repos. Only message me if there are failures or unusually long-running pipelines." --name "CI health" --announce --channel telegram --to "-1001234567890"
openclaw cron add "0 16 * * 5" "Friday sprint summary: Summarize the sprint progress. Issues completed, in progress, and not started. Velocity compared to target. Blockers and risks for next week." --name "Sprint summary" --announce --channel telegram --to "-1001234567890"

## Morning PR Digest — Tuesday, Feb 24
### Needs Your Review (2)
- **#345** Add rate limiting to API (by @alice, opened 2 days ago)
  CI: ✅ Passing | Size: +342/-28 | Labels: backend, security
- **#347** Fix user preferences migration (by @bob, opened yesterday)
  CI: ✅ Passing | Size: +56/-12 | Labels: database, bug
### Your Open PRs (1)
- **#342** Implement caching layer (opened 3 days ago)
  Reviews: 1 approved, 1 changes requested | CI: ✅ Passing
  → @carol requested changes on the cache invalidation logic
### Recently Merged (2)
- **#340** Update dependencies (merged yesterday by @alice)
- **#338** Add error tracking middleware (merged 2 days ago by you)

## End of Day Summary — Tuesday, Feb 24
### Commits Today: 7
**org/main-repo** (5 commits, +245/-89)
- abc1234 Implement cache invalidation for user sessions
- def5678 Add cache warm-up on application start
- ghi9012 Fix edge case in cache TTL calculation
- jkl3456 Add integration tests for caching layer
- mno7890 Address review comments on PR #342
**org/api-service** (2 commits, +34/-8)
- pqr1234 Update API docs for rate limiting
- stu5678 Fix typo in error message
### PRs: 1 opened, 0 merged, 2 reviews submitted
### Linear: 2 issues moved to Done, 1 moved to In Review