moth-cli 0.2.0 → 0.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +20 -3
  2. package/package.json +6 -6
package/README.md CHANGED
@@ -48,7 +48,24 @@ backlog
48
48
 
49
49
  Name a ticket however you remember it. `moth show 280f4d`, `moth show 280` and `moth show "ship the binary"` all find the same one, and an ambiguous reference lists the candidates rather than guessing.
50
50
 
51
- `moth --help` lists every command; each one's `--help` carries a worked example. `moth schema --json` reports exactly what this repository considers a legal ticket, which is how an agent learns the rules in one call.
51
+ `moth schema --json` reports exactly what this repository considers a legal ticket, which is how an agent learns the rules in one call.
52
+
53
+ ## Commands
54
+
55
+ Ten, and that is the whole surface:
56
+
57
+ - `init` — set up a repository
58
+ - `new` — file a ticket
59
+ - `list` — the default view, priority then age
60
+ - `show` — one ticket in full
61
+ - `move` — change status, which is how you claim work
62
+ - `edit` — change any field, the body included
63
+ - `delete` — remove a ticket
64
+ - `board` — a markdown board, grouped by status
65
+ - `check` — validate every ticket against the schema
66
+ - `schema` — this repository's rules, as JSON
67
+
68
+ Each one's `--help` carries its flags and a worked example, and `--json` is available on everything that returns a ticket.
52
69
 
53
70
  ## Why it exists
54
71
 
@@ -70,7 +87,7 @@ Every rejection, with its reasoning, is in [the spec](docs/spec-v1.md#out-of-sco
70
87
 
71
88
  ## Storage
72
89
 
73
- `moth.config.yml` at the root, and one markdown file per ticket in `.moth/`:
90
+ `moth.config.yml` at the root, and one markdown file per ticket in `.moth/`, named for its title so a directory listing reads like a backlog — `fix-the-login-redirect-280f4d.md`:
74
91
 
75
92
  ```markdown
76
93
  ---
@@ -94,7 +111,7 @@ Flat, with nothing central that every write touches, so two branches creating ti
94
111
  ## Design
95
112
 
96
113
  - [The v1 spec](docs/spec-v1.md) — what was built, and every rejected alternative
97
- - [Architecture decisions](docs/adr/) — including two reversals, with the reasoning that changed
114
+ - [Architecture decisions](docs/adr/) — four decisions, each with the alternatives that lost
98
115
  - [Contributing](CONTRIBUTING.md)
99
116
 
100
117
  moth tracks its own development in moth: the backlog is [`.moth/`](.moth/).
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "moth-cli",
3
- "version": "0.2.0",
3
+ "version": "0.3.1",
4
4
  "description": "An opinionated issue tracker that lives in your repo. Tickets are markdown files with an enforced schema.",
5
5
  "keywords": [
6
6
  "issue-tracker",
@@ -22,10 +22,10 @@
22
22
  "bin"
23
23
  ],
24
24
  "optionalDependencies": {
25
- "moth-cli-darwin-arm64": "0.2.0",
26
- "moth-cli-darwin-x64": "0.2.0",
27
- "moth-cli-linux-arm64": "0.2.0",
28
- "moth-cli-linux-x64": "0.2.0",
29
- "moth-cli-windows-x64": "0.2.0"
25
+ "moth-cli-darwin-arm64": "0.3.1",
26
+ "moth-cli-darwin-x64": "0.3.1",
27
+ "moth-cli-linux-arm64": "0.3.1",
28
+ "moth-cli-linux-x64": "0.3.1",
29
+ "moth-cli-windows-x64": "0.3.1"
30
30
  }
31
31
  }