@accord-dev/accord 0.4.1 → 0.5.0
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.
- package/README.md +11 -11
- package/dist/cli.js +3999 -695
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -8,7 +8,7 @@ Accord adds a small, fixed folder to your repository. Before an agent writes cod
|
|
|
8
8
|
|
|
9
9
|
BA, designer, developer and reviewer are four stages a ticket passes through, not four job titles. One person can pass through all four, or four people on a team can divide them. No gate reads who anyone is, so the same rules hold either way.
|
|
10
10
|
|
|
11
|
-
Released: `@accord-dev/accord@0.
|
|
11
|
+
Released: `@accord-dev/accord@0.5.0` on npm. See [docs/design.md](https://github.com/ngothanhluan/accord/blob/main/docs/design.md) for the design and the reasoning behind it.
|
|
12
12
|
|
|
13
13
|
## The problem
|
|
14
14
|
|
|
@@ -22,7 +22,7 @@ AI coding agents produce features that pass their own tests and still miss what
|
|
|
22
22
|
- A workflow shipped as skill files, one definition each, rendered for every coding agent you list: Claude Code, Codex, Cursor and Copilot.
|
|
23
23
|
- Lanes sized to the work, each ticket worked in its own git worktree. See [Usage](#usage).
|
|
24
24
|
- Tests as evidence, never as a claim. `accord task-done` and `accord gate done` read only the JUnit report that `tests.report` names in `config.yml`. The CLI never runs a test command itself.
|
|
25
|
-
- Trackers, design tools and a future multi-repo hub are adapters, never requirements. The default tracker is `none`.
|
|
25
|
+
- Trackers, design tools and a future multi-repo hub are adapters, never requirements. The default tracker is `none`. `tracker.adapter` also takes `github-issues` (`GITHUB_TOKEN`, or the `gh` CLI), `jira` (`JIRA_EMAIL` and `JIRA_API_TOKEN` for Cloud, or `JIRA_PAT` for Server and Data Center, with an https `url`), `linear` (`LINEAR_API_KEY`) and `script` (a `command` of your own that prints JSON). Tokens come from your environment and are never written to a file. Tracker data is display only: `accord status` shows title, state and labels, a failure is one warning, and it never changes a gate, a lint result or an exit code. See [docs/releases.md](https://github.com/ngothanhluan/accord/blob/main/docs/releases.md) for the script contract.
|
|
26
26
|
|
|
27
27
|
## What it is not
|
|
28
28
|
|
|
@@ -37,13 +37,13 @@ AI coding agents produce features that pass their own tests and still miss what
|
|
|
37
37
|
Node 22.12 or newer. Run accord through npx with an exact version, so nothing needs installing:
|
|
38
38
|
|
|
39
39
|
```sh
|
|
40
|
-
npx --yes @accord-dev/accord@0.
|
|
40
|
+
npx --yes @accord-dev/accord@0.5.0 <command>
|
|
41
41
|
```
|
|
42
42
|
|
|
43
43
|
Or install it globally and run `accord <command>`:
|
|
44
44
|
|
|
45
45
|
```sh
|
|
46
|
-
npm i -g @accord-dev/accord@0.
|
|
46
|
+
npm i -g @accord-dev/accord@0.5.0
|
|
47
47
|
```
|
|
48
48
|
|
|
49
49
|
The global install must be the same version the repository pins (see [Version pin](#7-version-pin-and-upgrading)).
|
|
@@ -53,7 +53,7 @@ The global install must be the same version the repository pins (see [Version pi
|
|
|
53
53
|
In the repository root:
|
|
54
54
|
|
|
55
55
|
```sh
|
|
56
|
-
npx --yes @accord-dev/accord@0.
|
|
56
|
+
npx --yes @accord-dev/accord@0.5.0 init
|
|
57
57
|
```
|
|
58
58
|
|
|
59
59
|
`init` asks nothing and takes no options. It never overwrites `accord/config.yml`, the product files or the workflow when they exist. The skill, agent and pane copies are accord's own and are rewritten to this version, and the hooks are merged into existing settings. Each path is printed as `created`, `skipped`, `appended`, `updated`, `unchanged` or `overwrote local edits`. It writes:
|
|
@@ -76,7 +76,7 @@ git commit -m "accord init"
|
|
|
76
76
|
git push
|
|
77
77
|
```
|
|
78
78
|
|
|
79
|
-
Teammates get the same skills, hooks and pane by pulling. The skills run a bare `accord` command. In Claude Code, the session hook tells the agent to run it through `npx` at the pinned version when `accord` is not on PATH. In Codex, Cursor and Copilot there is no such hook, so each person installs the pinned version globally (`npm i -g @accord-dev/accord@0.
|
|
79
|
+
Teammates get the same skills, hooks and pane by pulling. The skills run a bare `accord` command. In Claude Code, the session hook tells the agent to run it through `npx` at the pinned version when `accord` is not on PATH. In Codex, Cursor and Copilot there is no such hook, so each person installs the pinned version globally (`npm i -g @accord-dev/accord@0.5.0`).
|
|
80
80
|
|
|
81
81
|
### 4. Daily use in your coding agent
|
|
82
82
|
|
|
@@ -118,14 +118,14 @@ In Claude Code, the pane shows the dashboard beside the chat.
|
|
|
118
118
|
After you change `runtimes:`, write the copies again and commit what it prints:
|
|
119
119
|
|
|
120
120
|
```sh
|
|
121
|
-
npx --yes @accord-dev/accord@0.
|
|
121
|
+
npx --yes @accord-dev/accord@0.5.0 skills sync
|
|
122
122
|
```
|
|
123
123
|
|
|
124
124
|
`skills sync` deletes no copy you may still use. When you remove a runtime, it lists the copies it no longer writes, and you delete them yourself. The one file it deletes is `.claude/agents/accord-architect.md`, an agent accord no longer has, and only while its marker shows nobody edited it: it prints `removed` for it, and lists an edited copy with the others.
|
|
125
125
|
|
|
126
126
|
### 6. CLI commands for people and CI
|
|
127
127
|
|
|
128
|
-
The skills call the CLI for you. These are the commands most useful to run by hand or in CI. Bare `accord` needs the global install at the pinned version; without it, put `npx --yes @accord-dev/accord@0.
|
|
128
|
+
The skills call the CLI for you. These are the commands most useful to run by hand or in CI. Bare `accord` needs the global install at the pinned version; without it, put `npx --yes @accord-dev/accord@0.5.0` in place of `accord`. Run `accord --help` for the full list, and `accord <command> --help` for each one.
|
|
129
129
|
|
|
130
130
|
| Command | What it does |
|
|
131
131
|
|---|---|
|
|
@@ -145,15 +145,15 @@ The skills call the CLI for you. These are the commands most useful to run by ha
|
|
|
145
145
|
|
|
146
146
|
### 7. Version pin and upgrading
|
|
147
147
|
|
|
148
|
-
`accord/config.yml` pins an exact version in its `accord:` key, and the CI workflow and Claude Code hooks use the same one. Every command that reads the repository refuses with exit 2 when the running version differs (on a version mismatch the `prompt-expansion` and `pre-tool-use` hooks only warn, so the prompt or the agent dispatch goes on), and names the command to run instead, with the pinned version in place of 0.
|
|
148
|
+
`accord/config.yml` pins an exact version in its `accord:` key, and the CI workflow and Claude Code hooks use the same one. Every command that reads the repository refuses with exit 2 when the running version differs (on a version mismatch the `prompt-expansion` and `pre-tool-use` hooks only warn, so the prompt or the agent dispatch goes on), and names the command to run instead, with the pinned version in place of 0.5.0:
|
|
149
149
|
|
|
150
150
|
```sh
|
|
151
|
-
npx --yes @accord-dev/accord@0.
|
|
151
|
+
npx --yes @accord-dev/accord@0.5.0 <command>
|
|
152
152
|
```
|
|
153
153
|
|
|
154
154
|
There is no flag or environment variable that skips the check. Only `--version`, `--help` and `upgrade` run regardless.
|
|
155
155
|
|
|
156
|
-
`/accord` says when a newer release is out. `/accord upgrade` runs `upgrade` as the newer version, which pushes a branch `upgrade/<version>` from the remote default branch with one commit that moves the pin and regenerates the skill files. Your checkout is not touched; merge the pull request to upgrade. A repository still pinned to 0.1.0 runs `npx --yes @accord-dev/accord@0.
|
|
156
|
+
`/accord` says when a newer release is out. `/accord upgrade` runs `upgrade` as the newer version, which pushes a branch `upgrade/<version>` from the remote default branch with one commit that moves the pin and regenerates the skill files. Your checkout is not touched; merge the pull request to upgrade. A repository still pinned to 0.1.0 runs `npx --yes @accord-dev/accord@0.5.0 upgrade` once by hand.
|
|
157
157
|
|
|
158
158
|
Exit codes:
|
|
159
159
|
|