fledge 0.13.0

Dev-lifecycle CLI — scaffolding, tasks, lanes, plugins, and more.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

# Doctor: Environment Diagnostics

`fledge doctor` checks your environment for issues that might cause problems. Run it when something isn't working right, or proactively before starting a new project.

## Usage

```bash
fledge doctor
fledge doctor --json
```

## What It Checks

Doctor auto-detects your project type and checks relevant tools:

**Toolchain** (project-type-specific):

| Project type | What it checks |
|--------------|----------------|
| Rust | `rustc`, `cargo`, `cargo-clippy`, `rustfmt` |
| Node.js | `node`, `npm` or `yarn` |
| Go | `go` |
| Python | `python3` or `python`, `pip` |
| Ruby | `ruby`, `gem`, `bundler` |
| Java (Gradle) | `java`, `gradle` |
| Java (Maven) | `java`, `mvn` |
| Swift | `swift`, `swiftlint` (optional) |

**Dependencies** — checks for lockfiles and build artifacts (e.g. `Cargo.lock`, `node_modules/`, `go.sum`).

**Git** — `git` installed, repository initialized, remote configured, working tree status.

**AI** — `claude` CLI installed (enables `fledge review` and `fledge ask`).

## Output

Doctor reports each check as passing or failing:

- **Pass** (✅): tool is installed and working, with version info
- **Fail** (❌): tool is missing or errored, with a suggested fix command

## When to Run It

- Before your first `fledge templates init` to make sure your environment is ready
- When `fledge run` can't find the right command for your project type
- When GitHub commands (`issues`, `prs`, `checks`, `work pr`) fail with auth errors
- After upgrading your toolchain or switching machines

## JSON Output

```bash
fledge doctor --json
```

Returns a structured report for scripting or CI checks. Each entry includes the check name, status, version (if applicable), and any diagnostic message.