dobbe

dobbe setup

Interactive first-time setup wizard for dobbe.

Synopsis

dobbe setup [OPTIONS]

Options

Flag Description
--advanced Step-by-step setup with all options
--non-interactive No prompts - for CI/scripts (requires --org)
--org TEXT Default GitHub organization
--repos TEXT Comma-separated repo paths, or auto to scan
--schedule TEXT Preset schedule: daily-vuln, weekly-review
--skip-first-command Skip guided first-scan prompt

Description

dobbe setup configures dobbe for first use. It auto-detects your environment (Claude CLI, authentication, MCP servers, GitHub org, local repos) and saves everything to ~/.dobbe/config.toml.

There are three onboarding paths:

Skill Auto-Installation

On every dobbe invocation (including after setup completes), dobbe automatically installs or updates bundled Claude Code skills to ~/.claude/skills/. Skills are .md files that Claude Code discovers as slash commands. They are refreshed whenever the dobbe package version changes, so upgrading dobbe automatically brings new or improved skills.

Setup Paths

                    dobbe setup
                         |
         +---------------+---------------+
         |               |               |
         v               v               v
   QuickStart        Advanced       Non-Interactive
   (default)       (--advanced)   (--non-interactive)
         |               |               |
         v               v               v
   Auto-detect       Auto-detect     Validate --org
   environment       environment     Resolve --repos
         |               |               |
         v               v               v
   Show summary      Step 1-5         Build config
   Ask: Accept?      interactive           |
     |    |          prompts               v
     Y    C->           |            Save + done
     |   Advanced       v
     v               Step 6:
   Save config       Schedule?
         |               |
         v               v
   Print next        Step 7:
   steps             MCP help
                         |
                         v
                    Save config
                    Smoke test
                    Print next steps

QuickStart (default)

Runs a single auto-detection pass behind a spinner, then displays a summary:

You are prompted to accept, decline, or customize. Choosing “customize” switches to the Advanced flow.

Advanced (--advanced)

Walks through each step with interactive prompts:

  1. Claude Code CLI - verify claude is on PATH
  2. Authentication - verify Claude Code is authenticated
  3. MCP Discovery - list available/missing MCP servers; check gh CLI fallback
  4. Configuration - prompt for default GitHub org (pre-filled from auto-detect); verify the org exists on GitHub via gh api
  5. Local repositories - show discovered repos, select which to include (enter numbers, all, or none)
  6. Schedule setup (optional) - offer to create a daily-vuln or weekly-review schedule preset
  7. MCP install guidance - print setup instructions for any missing MCPs

After saving, a smoke test verifies the config, GitHub access, and MCP availability.

Non-Interactive (--non-interactive)

Designed for CI pipelines and scripted provisioning. Requires --org:

dobbe setup --non-interactive --org my-org --repos auto --schedule daily-vuln

No prompts are issued. Repos default to auto-scan if --repos is omitted.

Re-running Setup

Running dobbe setup again is safe. When an existing config is detected, you are offered three choices:

  1. Re-detect and update - re-scan the environment and merge into current config (keeps customizations like notification settings)
  2. Start fresh - back up the current config and create a new one
  3. Cancel

Sample Config Output

After setup, ~/.dobbe/config.toml looks like:

[general]
default_org = "nareshnavinash"
default_format = "table"
default_severity = "critical,high"

[notifications]
slack_channel = ""

[repos]
local_paths = [
    "/Users/you/projects/api",
    "/Users/you/projects/web",
]

See Also