fledge 0.15.1

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
56
57
58
59

# The Six Pillars

fledge organizes your dev workflow into six pillars. They cover the whole lifecycle from project creation to release, and they're explicitly the *only* things core ships. Anything else is a plugin.

```
Scaffold --> Run --> Spec --> AI --> Ship
                                       \
                  Extend (the protocol that lets plugins add the rest)
```

## Scaffold

Get a project off the ground. Pick a template (built-in or remote), scaffold it, and you're writing code in under a minute.

**Commands:** `templates init`, `templates create`, `templates validate`, `templates list`

For remote template search and publishing — `templates-search`, `templates-publish` — install [`fledge-plugin-templates-remote`](https://github.com/CorvidLabs/fledge-plugin-templates-remote). It ships in the default plugin set (`fledge plugins install --defaults`).

## Run

Define your tasks, wire them into pipelines, watch files for re-runs. This is where `fledge.toml` lives.

**Commands:** `run`, `lanes`, `watch`

## Spec

spec-sync: every module declares a contract (`specs/<name>/<name>.spec.md` plus optional companion files). The contract is the source of truth for *why* a module exists, and AI commands inject the relevant specs as context. Your code and your docs literally cannot drift.

**Commands:** `spec` (subcommands: `check`, `init`, `list`, `show`, `new`)

## AI

Provider-agnostic AI in the daily-driver path. Switch between Claude CLI and any Ollama-speaking endpoint in one line; ask questions about your codebase; review your diff with one model or a panel of them in parallel.

**Commands:** `ai` (`status`, `models`, `use`), `ask`, `review`

## Ship

Branch, draft an AI-written PR body, preview, confirm, push. Then bump version, generate changelog, tag, push the tag.

**Commands:** `work` (`start`, `pr`, `status`), `release`, `changelog`

For GitHub-specific browsing of the resulting PR/checks/issues, install [`fledge-plugin-github`](https://github.com/CorvidLabs/fledge-plugin-github). Ships in the default plugin set.

## Extend

Plugins, configuration, command-tree introspection, environment diagnostics, shell completions. The mechanism layer.

**Commands:** `plugins`, `config`, `introspect`, `completions`, `doctor`

`fledge plugins install --defaults` installs the curated set of plugins that took over commands removed from core in v0.15:

- [`fledge-plugin-github`](https://github.com/CorvidLabs/fledge-plugin-github) → `checks`, `issues`, `prs`
- [`fledge-plugin-deps`](https://github.com/CorvidLabs/fledge-plugin-deps) → `deps`
- [`fledge-plugin-metrics`](https://github.com/CorvidLabs/fledge-plugin-metrics) → `metrics`
- [`fledge-plugin-templates-remote`](https://github.com/CorvidLabs/fledge-plugin-templates-remote) → `templates-search`, `templates-publish`
- [`fledge-plugin-doctor`](https://github.com/CorvidLabs/fledge-plugin-doctor) → `doctor-tools`

Why these are plugins, not core: each one bakes an ecosystem assumption (GitHub-only, polyglot lockfile parsers, niche metrics) that not every fledge user needs. Plugins keep the binary small and let each capability evolve independently.