flux-platform 0.4.0

A local-first, AI-native developer automation platform: build, test, package, and deploy from a single .flux file, and make your repository legible to AI agents.
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
60

# GitHub integration

Flux integrates with GitHub **locally**. It is not a hosted GitHub App — that
would need a server Flux deliberately doesn't run (see the non-goals in
[architecture.md](architecture.md)). Instead Flux does the parts that are honest
offline, and enriches them with the [`gh` CLI](https://cli.github.com) when it's
installed and authenticated.

Flux never *posts* to GitHub on your behalf. Anything that publishes (a PR
comment, an issue) is left as an explicit `gh` command you run.

## `flux github init`

Scaffolds continuous integration:

```
flux github init            # write CI workflow + PR template
flux github init --force    # overwrite existing files
```

Writes:

- `.github/workflows/flux.yml` — runs `flux fmt`, `flux lint`, `flux verify`, and
  `flux build` on pushes and pull requests.
- `.github/pull_request_template.md` — a checklist referencing `flux verify` and
  `flux agent run reviewer`.

Existing files are skipped unless `--force` is passed.

## `flux github review`

```
flux github review          # review the working-tree diff
flux github review --pr 42   # review PR #42 (requires `gh`)
```

Without `--pr`, this runs the **reviewer** agent over your working tree: it
summarises changed files and flags source changes that lack a matching test
change. With `--pr N` it reads the PR's file list via `gh pr diff` (and fails
honestly if `gh` isn't installed). The report is written to
`.flux-cache/reports/`.

## `flux github plan`

```
flux github plan "add a notifications system"
flux github plan --issue 17    # fetch the issue title via `gh`
```

Turns a description — or a GitHub issue's title, fetched with `gh` — into a
structured implementation-plan skeleton via the **planner** agent (schema →
service → CLI/API → tests → docs). It's a scaffold for an AI or human to flesh
out; set `ai.command` in `flux.yaml` to have an external model expand each step
against your codebase.

## Honest degradation

Every command works without `gh` — you just lose the GitHub-specific reads (PR
diffs, issue titles). Flux tells you when `gh` would help rather than pretending
it succeeded.