@activatus/code-standards 3.0.8 โ†’ 3.1.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 CHANGED
@@ -27,14 +27,14 @@ Ours live here. If it's not in this repo, it's not a standard, it's an opinion.
27
27
  The standards ship as an npm package, published on npm (npmjs.com) and installed with pnpm, so an AI agent reads the exact version a project uses, straight from `node_modules`:
28
28
 
29
29
  ```bash
30
- pnpm add -D @activatus/code-standards
30
+ pnpm add -D @activatus/code-standards@latest
31
31
  ```
32
32
 
33
33
  Then tell your agent: **"Follow the Activatus Code Standards. Start with `node_modules/@activatus/code-standards/docs/Guides/setup.md`."** It prints a numbered list of the standards, you say which ones you don't want, and it sets up the rest. You never touch the terminal.
34
34
 
35
35
  The package version is the standards version: `3.0.0` is version 3.
36
36
 
37
- > ๐Ÿ”ข **Updating a project to newer standards?** Run `pnpm update @activatus/code-standards --latest`, then point the agent at the **[Version History](https://activatus-code-standards.vercel.app/docs/version-history)**: it reads only the versions newer than the project's, does exactly what each one says, and bumps the number. Cheaper than shouting the whole pub a round.
37
+ > ๐Ÿ”ข **Updating a project to newer standards?** Run `pnpm add -D @activatus/code-standards@latest`, then point the agent at the **[Version History](https://activatus-code-standards.vercel.app/docs/version-history)**: it reads only the versions newer than the project's, does exactly what each one says, and bumps the number. Cheaper than shouting the whole pub a round.
38
38
 
39
39
  ---
40
40
 
@@ -30,7 +30,7 @@ Add `prettier.config.mjs` โ€” see the [Prettier page](/docs/Standards/prettier)
30
30
  Format everything at once:
31
31
 
32
32
  ```bash
33
- pnpm prettier --write .
33
+ pnpm format
34
34
  ```
35
35
 
36
36
  Keep the reformat apart from any other change, so the formatting is easy to tell apart from real changes later.
@@ -14,9 +14,11 @@ The person creates the app themselves โ€” with `create-next-app`, Expo or anythi
14
14
  ## 1. Install the standards
15
15
 
16
16
  ```bash
17
- pnpm add -D @activatus/code-standards
17
+ pnpm add -D @activatus/code-standards@latest
18
18
  ```
19
19
 
20
+ **Always install with `@latest`, never a typed version number.** `package.json` keeps whatever version pnpm writes.
21
+
20
22
  **If pnpm refuses because the version is too new**, that is pnpm's `minimumReleaseAge` setting: by default it will not install a version published less than a day ago. The standards come from us, so add the package to `minimumReleaseAgeExclude` in `pnpm-workspace.yaml`:
21
23
 
22
24
  ```yaml title="pnpm-workspace.yaml"
@@ -24,7 +26,7 @@ minimumReleaseAgeExclude:
24
26
  - "@activatus/code-standards"
25
27
  ```
26
28
 
27
- Newer pnpm versions may add this exclusion for you when you run `pnpm add`. Check the file either way, and add it if it is not there: `pnpm update` hits the same check when a new version of the standards has only just been published.
29
+ Newer pnpm versions may add this exclusion for you when you run `pnpm add`. Check the file either way, and add it if it is not there: an update hits the same check when a new version of the standards has only just been published. The entry is the plain package name, with no version. If pnpm wrote one with versions in it, such as `'@activatus/code-standards@3.0.4 || 3.0.5'`, replace it with the plain name: otherwise pnpm adds another version to it on every update.
28
30
 
29
31
  **pnpm owns `pnpm-workspace.yaml`** and rewrites it on every install, with single quotes, so `pnpm format:check` would fail after every update. Add the file to `.prettierignore`:
30
32
 
@@ -108,12 +110,14 @@ The list has nothing about branches or commit messages. Those are the project's
108
110
 
109
111
  ### Working with the agent
110
112
 
111
- Once the standards are agreed, get the **project links**:
113
+ Once the standards are agreed, offer the four [Working with Agents](/docs/Standards/working-with-agents) options. All four are optional: offer every one, every time, so the person can fill them in quickly and keep going.
114
+
115
+ First the **project links**. Find each one yourself, then ask the person to confirm it or say "None":
112
116
 
113
- - **GitHub repo:** read it with `git remote get-url origin` and ask the person to confirm it. If there is no remote, ask for it.
114
- - **Linear project:** if the project's own docs already name it, read it from there and ask the person to confirm it. Otherwise ask. Never copy it from another project. Write the workspace, the project and the ticket prefix, or "None" if the project does not use Linear.
117
+ - **GitHub repo:** read it with `git remote get-url origin`. If there is no remote, ask for it.
118
+ - **Linear project:** read it from the project's own docs if they name it: the workspace, the project and the ticket prefix. If they do not, ask. Never copy it from another project.
115
119
 
116
- Then **print this to the person exactly as it is written**:
120
+ Then the **status circles**. **Print this to the person exactly as it is written**:
117
121
 
118
122
  ```text
119
123
  Status circles (optional). Want the agent to report each
@@ -126,7 +130,14 @@ ticket as one line, with a circle that says if you need to act?
126
130
  Yes or no?
127
131
  ```
128
132
 
129
- **Record the answers** in the "Project workflow" section of `AGENTS.md`, from the template: the project links, and the status circles if they said yes. Delete the status circles section if they said no. Write the answer in `docs/development/coding-standards.md`, under "Details", so a later update knows not to ask again. See [Working with Agents](/docs/Standards/working-with-agents).
133
+ Then **ask before committing**. **Print this to the person exactly as it is written**:
134
+
135
+ ```text
136
+ Would you like AI to ask you before every commit and push
137
+ to git? Yes or no?
138
+ ```
139
+
140
+ **Record the answers** in the "Project workflow" section of `AGENTS.md`, from the template: each link they confirmed, and the status circles if they said yes. Delete the line for any link they said "None" to, and the status circles section if they said no. If they said yes to asking before committing, write under **Who commits**: "Ask the person before every commit and push, and wait for a clear yes to that specific action. A yes covers one action only." If they said no, write nothing about it: the agent uses its own judgement. Write all four answers in `docs/development/coding-standards.md`, under "Details", so a later update knows not to ask again. See [Working with Agents](/docs/Standards/working-with-agents).
130
141
 
131
142
  ## 4. Apply the standards
132
143
 
@@ -139,7 +150,7 @@ Do only the standards the person agreed to. Copy every file from `node_modules/@
139
150
  | Standard | What to set up |
140
151
  | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
141
152
  | 6. ESLint | Copy the config for the project's framework from `static/templates/eslint/`: `base`, `typescript`, `react` or `nextjs`. Install the packages listed on the [ESLint page](/docs/Standards/eslint). Add the scripts `"lint": "eslint ."` and `"lint:fix": "eslint . --fix"` |
142
- | 7. Prettier | `pnpm add -D prettier prettier-plugin-tailwindcss`. Copy `static/templates/prettier.config.mjs`. Add the scripts `"format": "prettier --write ."` and `"format:check": "prettier --check ."` |
153
+ | 7. Prettier | `pnpm add -D prettier prettier-plugin-tailwindcss`. Copy `static/templates/prettier.config.mjs`. Add the `format` and `format:check` scripts exactly as on the [Prettier page](/docs/Standards/prettier#usage) |
143
154
  | 8. Stylelint | Only if the project has hand-written CSS or SCSS. Copy the config from `static/templates/stylelint/css/` or `scss/`. See [Stylelint](/docs/Standards/stylelint) |
144
155
  | 9. EditorConfig | Copy `static/templates/.editorconfig` |
145
156
  | 10. Node version | Copy `static/templates/.nvmrc` and `static/templates/.envrc`. See [direnv + nvm](/docs/Standards/direnv) |
@@ -162,16 +173,16 @@ The other standards are rules for how code is written. There is nothing to insta
162
173
 
163
174
  The project already follows the standards, and a newer version is out.
164
175
 
165
- **A patch keeps the same version number.** When only the last number changes, such as 3.0.0 โ†’ 3.0.1, the project's version in `AGENTS.md` stays the same, but there may still be work to do. Update the package, then read that version's **Fixes** list and do anything it asks for the project's version. Check it every time the package is updated, even when the version number has not changed.
176
+ **A patch keeps the same version number.** When only the last or middle number changes, such as 3.0.0 โ†’ 3.0.1 or 3.0.9 โ†’ 3.1.0, the project's version in `AGENTS.md` stays the same, but there may still be work to do. Update the package, then read that version's **Fixes** list and do anything it asks for the project's version. Check it every time the package is updated, even when the version number has not changed.
166
177
 
167
178
  1. **Note the project's version.** Read `**Code standards version:**` in `AGENTS.md`. This is the version the code follows.
168
179
  2. **Update the package:**
169
180
 
170
181
  ```bash
171
- pnpm update @activatus/code-standards --latest
182
+ pnpm add -D @activatus/code-standards@latest
172
183
  ```
173
184
 
174
- Its major version is now the newest version. If pnpm refuses because the version is too new, or `pnpm format:check` now fails on `pnpm-workspace.yaml`, see [1. Install the standards](#1-install-the-standards).
185
+ Its major version is now the newest version. If pnpm refuses because the version is too new, or `pnpm format:check` now fails on `pnpm-workspace.yaml`, see [1. Install the standards](#1-install-the-standards). Check `minimumReleaseAgeExclude` in `pnpm-workspace.yaml` is the plain name, `"@activatus/code-standards"`, with no version in it.
175
186
 
176
187
  3. **Read `node_modules/@activatus/code-standards/docs/version-history.md`**, but only the versions newer than the project's. Do not re-read the rest of the standards.
177
188
  4. **Skip any change to a standard the project opted out of.** The opt-outs are listed in `docs/development/coding-standards.md`.
@@ -13,7 +13,7 @@ Every Activatus repository must have an `AGENTS.md` in its root. This file gives
13
13
 
14
14
  Each project writes them up in its own docs, usually in `docs/development/`, and its `AGENTS.md` has a **Project workflow** section that points to them and states the rules an agent must follow. The most important one goes first: whether an agent may commit.
15
15
 
16
- Project workflow also records the project's **GitHub repo** and **Linear project**, and the [status circles](/docs/Standards/working-with-agents#status-circles) if the project chose them during setup.
16
+ Project workflow also records whichever [Working with Agents](/docs/Standards/working-with-agents) options the project chose during setup: its **GitHub repo**, its **Linear project**, the **status circles**, and whether agents **ask before every commit and push** (written under Who commits). All four are optional; delete the line or section for any the project does not use.
17
17
 
18
18
  ## Template
19
19
 
@@ -51,12 +51,34 @@ Add scripts to `package.json`:
51
51
  ```json
52
52
  {
53
53
  "scripts": {
54
- "format": "prettier --write .",
55
- "format:check": "prettier --check ."
54
+ "format": "git ls-files -z --cached --others --exclude-standard | xargs -0 prettier --write --ignore-unknown --no-error-on-unmatched-pattern",
55
+ "format:check": "git ls-files -z --cached --others --exclude-standard | xargs -0 prettier --check --ignore-unknown --no-error-on-unmatched-pattern"
56
56
  }
57
57
  }
58
58
  ```
59
59
 
60
+ **Do not shorten these to `prettier --write .` and `prettier --check .`** The long form is deliberate: git lists the files, so every git ignore rule applies. See [What Prettier skips](#what-prettier-skips).
61
+
62
+ ## What Prettier skips
63
+
64
+ Both scripts work on the same list of files: every file git tracks, plus every new file git has not been told to ignore. **Never narrow them to changed files**: a badly formatted file nobody touched still fails CI.
65
+
66
+ **Why git lists the files.** On its own, Prettier reads only the project's `.gitignore` and `.prettierignore`. It does not read `.git/info/exclude` or a person's global git ignore, such as `~/.config/git/ignore`. Files a person keeps out of git that way, such as `.claude/settings.local.json`, would be checked by `prettier --check .` and rewritten by `prettier --write .`, so `format:check` failed on that one machine while CI passed. `git ls-files --exclude-standard` applies every git ignore rule, so those files never reach Prettier. `--no-error-on-unmatched-pattern` stops a file deleted but not yet committed from causing an error.
67
+
68
+ **Where each kind of file is ignored:**
69
+
70
+ | File | Where it goes |
71
+ | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
72
+ | One person's local tool files, such as `.claude/settings.local.json` | That person's `.git/info/exclude` or global git ignore. Never `.prettierignore` |
73
+ | Files the whole project keeps out of git, such as `build/` | `.gitignore` |
74
+ | Files in git that Prettier must not format, such as `pnpm-workspace.yaml` | `.prettierignore`, shared by the whole project |
75
+
76
+ pnpm rewrites `pnpm-workspace.yaml` in its own style on every install, so it always goes in `.prettierignore`:
77
+
78
+ ```text title=".prettierignore"
79
+ pnpm-workspace.yaml
80
+ ```
81
+
60
82
  ## Tailwind class sorting
61
83
 
62
84
  The config includes [`prettier-plugin-tailwindcss`](https://github.com/tailwindlabs/prettier-plugin-tailwindcss), the official Tailwind plugin. It sorts the classes in every `className` into one standard order when the file is formatted, so the same classes are always written the same way:
@@ -5,13 +5,13 @@ sidebar_label: "Working with Agents"
5
5
 
6
6
  # Working with Agents
7
7
 
8
- > How an AI agent links a project's work and reports on it. The project links are part of every setup; the status circles are optional, chosen during [Setup](/docs/Guides/setup#working-with-the-agent). Both work the same with Claude Code, ChatGPT, Codex or any agent that reads `AGENTS.md`.
8
+ > How an AI agent links a project's work, reports on it and asks before committing. The GitHub repo, the Linear project, the status circles and asking before every commit and push are all optional. [Setup](/docs/Guides/setup#working-with-the-agent) offers all four every time, so they take a moment to fill in, and a project can leave out any of them. They work the same with Claude Code, ChatGPT, Codex or any agent that reads `AGENTS.md`.
9
9
 
10
10
  Whatever the project chooses is written into the **Project workflow** section of its `AGENTS.md`, from the [template](/docs/templates#agents), so every agent in the project follows it.
11
11
 
12
12
  ## Project links
13
13
 
14
- Every project records these two links in **Project workflow**. An agent uses them to link tickets and Pull Requests, and to know where work belongs.
14
+ Optional. A project records either link, both or neither, in **Project workflow**, and deletes the line for any link it does not use. An agent uses them to link tickets and Pull Requests, and to know where work belongs.
15
15
 
16
16
  | Link | Where it comes from |
17
17
  | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -42,4 +42,6 @@ Optional. An agent reports the state of every ticket or piece of work as one lin
42
42
  - **No ticket is fine.** Work without one is just the circle and a short title.
43
43
  - **Only what the person needs.** Leave out anything they already know.
44
44
 
45
- Whether and when agents commit is not part of this. It is the project's own workflow, under **Who commits** in Project workflow.
45
+ ## Ask before committing
46
+
47
+ Optional. Setup asks: "Would you like AI to ask you before every commit and push to git?" A yes is written under **Who commits** in Project workflow: ask the person before every commit and push, and wait for a clear yes to that specific action. A yes covers one action only. A no means nothing is written, and the agent uses its own judgement.
package/docs/intro.md CHANGED
@@ -22,7 +22,7 @@ This site documents the shared code standards used across all Activatus projects
22
22
  | EditorConfig | [`.editorconfig`](/docs/Standards/editorconfig) | Editor-level whitespace rules |
23
23
  | direnv + nvm | [`.envrc` / `.nvmrc`](/docs/Standards/direnv) | Automatic Node version switching on `cd` |
24
24
  | AGENTS.md | [`AGENTS.md`](/docs/Standards/agent-specs) | AI agent context and agent skills |
25
- | Working with Agents | [Optional](/docs/Standards/working-with-agents) | The project's GitHub repo and Linear project, and optional status circles |
25
+ | Working with Agents | [Optional](/docs/Standards/working-with-agents) | GitHub repo, Linear project, status circles and asking before commits: all optional |
26
26
  | CSS Styling | [Styling guide](/docs/Standards/styling) | Tailwind CSS, flexbox-first layout and global colour variables |
27
27
  | Tech Stack | [Tech stack](/docs/Standards/tech-stack) | The frameworks, libraries and versions we build on |
28
28
 
@@ -18,14 +18,14 @@ sidebar_label: "Version History"
18
18
  **Read only the versions newer than the project's.** A project on version 1 that is updating to version 3 reads version 2 and version 3 on this page, and nothing else. Do not re-read every standard or check the whole codebase: each version lists every change that matters, and how to find the code it affects.
19
19
 
20
20
  1. **Find the project's version** in its `AGENTS.md`. If there is none, the project has never followed the standards: follow [Setup](/docs/Guides/setup) instead.
21
- 2. **Update the package:** `pnpm update @activatus/code-standards --latest`. If pnpm refuses because the version is too new, add the package to `minimumReleaseAgeExclude` in `pnpm-workspace.yaml`, as in [Setup](/docs/Guides/setup#1-install-the-standards). Then read this page from `node_modules/@activatus/code-standards/docs/version-history.md`.
21
+ 2. **Update the package:** `pnpm add -D @activatus/code-standards@latest`, never a typed version number. If pnpm refuses because the version is too new, add the package to `minimumReleaseAgeExclude` in `pnpm-workspace.yaml`, as in [Setup](/docs/Guides/setup#1-install-the-standards). The entry is the plain package name, with no version. If pnpm wrote one with versions in it, such as `'@activatus/code-standards@3.0.4 || 3.0.5'`, replace it with the plain name: otherwise pnpm adds another version to it on every update. Then read this page from `node_modules/@activatus/code-standards/docs/version-history.md`.
22
22
  3. **Read each version newer than the project's**, oldest first. Skip any change to a standard the project opted out of: they are listed in `docs/development/coding-standards.md`.
23
23
  4. **For each change, do the "What to do" steps**, then run the "How to check" searches. A search that still finds something means the change is not finished. When a change says to copy a line from the `AGENTS.md` template, and the project's `AGENTS.md` records the standards in its own words instead, write the updated rule there in the project's own shape.
24
24
  5. **Strike out what the standard now covers.** After the changes, re-read the project's list of opted-out and changed standards in `docs/development/coding-standards.md`. Take off the list any exception the new version has made part of the standard, and update any rule it records for an old shape of the standard. A differences list that still describes the old standard sends the next agent wrong.
25
- 6. **Run `pnpm lint`, `pnpm test` and the build** after each change.
25
+ 6. **Run `pnpm lint`, `pnpm format:check`, `pnpm test` and the build** after each change. `format:check` checks every file git does not ignore; never narrow it to changed files.
26
26
  7. **Update the version number** in `AGENTS.md` once every change is done.
27
27
 
28
- **A patch keeps the same version number.** When only the last number changes, such as 3.0.0 โ†’ 3.0.1, the project's version in `AGENTS.md` stays the same, but there may still be work to do. Update the package, then read that version's **Fixes** list and do anything it asks for the project's version. Check it every time the package is updated, even when the version number has not changed.
28
+ **A patch keeps the same version number.** When only the last or middle number changes, such as 3.0.0 โ†’ 3.0.1 or 3.0.9 โ†’ 3.1.0, the project's version in `AGENTS.md` stays the same, but there may still be work to do. Update the package, then read that version's **Fixes** list and do anything it asks for the project's version. Check it every time the package is updated, even when the version number has not changed.
29
29
 
30
30
  **When a change does not fit the project**, for example it renames a folder the project does not have, skip it. If you are not sure, ask; do not guess.
31
31
 
@@ -41,6 +41,8 @@ Anyone changing the standards adds a version, alongside the change:
41
41
  - **Work in progress goes under `## Version N โ€” not released yet`**, with a line saying projects should not apply it yet. Changes can be added to it over time. To release it: pilot it (below), drop "not released yet", add the **Released** date and **Updates from** line, set `package.json` to `N.0.0`, then publish.
42
42
  - **Pilot a version in a real project before releasing it.** Once the work-in-progress version is written, have one real project apply it exactly as written, reading only what the page says. Every judgement call the agent has to make, and every instruction that does not fit the project, is a missing sentence: fold it back into the version before publishing. Release only when the pilot runs without the agent asking a question the page does not answer.
43
43
  - **Fixing a released version** bumps only the last number: `3.0.0` โ†’ `3.0.1`. Update the version's changes in place, and list what was fixed under its **Fixes**. Projects keep the same version number in `AGENTS.md`. Write each fix so a project already on that version knows what to do.
44
+ - **Adding something optional** to a released version, such as a new setup question, bumps the middle number: `3.0.9` โ†’ `3.1.0`. It is written up the same way as a fix, and projects keep the same version number in `AGENTS.md`.
45
+ - **Every release commit is titled `docs: version N.N.N โ€” <what changed>`**, such as `docs: version 3.0.9 โ€” optional project links`, so releases are easy to find in the git log.
44
46
  - **Every patch number is published.** Publish each patch to npm as soon as its Fixes are written. A Fixes entry for a version that was never published sends a project to install something that does not exist.
45
47
  - **Judgement calls after release are fixes, not workarounds.** When a project's update needed a call the steps did not cover, add it under the version's Fixes so every other project gets it too. A project should never keep a private workaround for an unclear step.
46
48
 
@@ -48,13 +50,39 @@ Anyone changing the standards adds a version, alongside the change:
48
50
 
49
51
  ## Version 3
50
52
 
51
- **Released:** 2026-10-17 ยท **Updates from:** version 2 ยท **Latest fix:** 3.0.8
53
+ **Released:** 2026-10-17 ยท **Updates from:** version 2 ยท **Latest fix:** 3.1.0
52
54
 
53
- Install it with `pnpm add -D @activatus/code-standards@3.0.8`. Do change 1 first: it says which parts of the project's `AGENTS.md` are now the project's own to write.
55
+ Install it with `pnpm add -D @activatus/code-standards@latest`. Do change 1 first: it says which parts of the project's `AGENTS.md` are now the project's own to write.
56
+
57
+ **Fixes in 3.1.0.** If the project already applied 3.0.9, check these:
58
+
59
+ - **Install and update with `@latest`.** Use `pnpm add -D @activatus/code-standards@latest`, never a typed version number. `package.json` keeps whatever version pnpm writes. Nothing to change in the project.
60
+ - **`minimumReleaseAgeExclude` is the plain package name.** In `pnpm-workspace.yaml`, the entry is `"@activatus/code-standards"`, with no version. If it has versions in it, such as `'@activatus/code-standards@3.0.4 || 3.0.5'`, replace it with the plain name. Otherwise pnpm adds another version on every update.
61
+ - **Setup asks whether AI should ask before every commit and push.** It is optional, a yes or no, recorded under **Who commits** in Project workflow. Ask the person the [question](/docs/Guides/setup#working-with-the-agent). A yes is written under Who commits; a no writes nothing, and the agent uses its own judgement. Write their answer in `docs/development/coding-standards.md`, under "Details".
62
+
63
+ **How to check:** `minimumReleaseAgeExclude` lists `"@activatus/code-standards"` with no version, running `pnpm add -D @activatus/code-standards@latest` again leaves `pnpm-workspace.yaml` unchanged, and if the person said yes, Who commits in `AGENTS.md` has the asking rule.
64
+
65
+ **Fixes in 3.0.9.** If the project already applied 3.0.8, check these:
66
+
67
+ - **The project links are optional, like the status circles.** The GitHub repo, the Linear project and the status circles are all optional, and setup offers all three every time. If the project does not use a link, delete its line from Project workflow in `AGENTS.md`. Record all three answers in `docs/development/coding-standards.md`, under "Details". An agent still never copies a Linear workspace or ticket prefix from another project: if `AGENTS.md` does not name the Linear project, it asks before creating, linking or citing any ticket.
68
+ - **`format` and `format:check` get their files from git.** Prettier reads the project's `.gitignore` and `.prettierignore`, but not `.git/info/exclude` or a person's global git ignore, so local tool files kept out of git that way, such as `.claude/settings.local.json`, made `pnpm format:check` fail on that machine only, and `pnpm format` rewrote them. Replace both scripts in `package.json`:
69
+
70
+ ```json
71
+ "format": "git ls-files -z --cached --others --exclude-standard | xargs -0 prettier --write --ignore-unknown --no-error-on-unmatched-pattern",
72
+ "format:check": "git ls-files -z --cached --others --exclude-standard | xargs -0 prettier --check --ignore-unknown --no-error-on-unmatched-pattern"
73
+ ```
74
+
75
+ Do not shorten them back to `prettier --write .` or `prettier --check .`. See [What Prettier skips](/docs/Standards/prettier#what-prettier-skips).
76
+
77
+ - **Take local tool files back out of `.prettierignore`.** If the project added files that are kept out of git only on someone's machine, such as `.claude/settings.local.json` or `.impeccable/*.local.json`, remove them: git's ignore rules cover them now. Keep entries for files in git that a tool rewrites, such as `pnpm-workspace.yaml`.
78
+ - **The 3.0.8 fix for option B missed a line.** If 3.0.7 also put "Ask before every commit and push" at the very top of `AGENTS.md`, remove that line too, unless the person wants to keep it as the project's own "Who commits" rule.
79
+ - Nothing to do in a project: release commits are titled `docs: version N.N.N โ€” <what changed>`.
80
+
81
+ **How to check:** `AGENTS.md` has no line for a project link the person said "None" to, and no "Ask before every commit and push" line unless the person kept it. `docs/development/coding-standards.md` records the answer for each of the three options. Both scripts in `package.json` start with `git ls-files`, `.prettierignore` has no local tool files, and `pnpm format:check` passes.
54
82
 
55
83
  **Fixes in 3.0.8.** If the project already applied 3.0.7, check these:
56
84
 
57
- - **Ask before every commit and push (option B) is gone.** Whether agents commit is the project's own workflow, as in change 1. If the project took B in 3.0.7, the rule stays only if the person wants it: it belongs under **Who commits** in Project workflow, in the project's own words. Remove the "Ask before every commit and push" section copied from the template, and take B off `docs/development/coding-standards.md`.
85
+ - **Ask before every commit and push (option B) is gone.** Whether agents commit is the project's own workflow, as in change 1. If the project took B in 3.0.7, the rule stays only if the person wants it: it belongs under **Who commits** in Project workflow, in the project's own words. Remove the "Ask before every commit and push" section copied from the template. 3.0.7 also put the rule at the very top of `AGENTS.md`: remove that line too, unless the person wants to keep it as the project's own "Who commits" rule. Take B off `docs/development/coding-standards.md`.
58
86
  - **The Linear project can come from the project's own docs.** If they already name it, read it from there and confirm it with the person. Never copy it from another project.
59
87
  - **`pnpm-workspace.yaml` is Prettier-ignored.** pnpm rewrites it with single quotes on every install, so `pnpm format:check` failed after every update. Add `pnpm-workspace.yaml` to `.prettierignore`.
60
88
  - **The update steps cover pnpm's release-age check**: if pnpm refuses a version that has only just been published, add the package to `minimumReleaseAgeExclude`. See [Setup](/docs/Guides/setup#1-install-the-standards).
@@ -64,10 +92,10 @@ Install it with `pnpm add -D @activatus/code-standards@3.0.8`. Do change 1 first
64
92
 
65
93
  **Fixes in 3.0.7.** New, optional: [Working with Agents](/docs/Standards/working-with-agents). Setup now asks for the project's GitHub repo and Linear project, and offers status circles. (3.0.7 also offered asking before every commit and push. 3.0.8 removed it.) If the project already applied 3.0.5:
66
94
 
67
- - Add **GitHub repo** and **Linear project** to the Project workflow section of `AGENTS.md`, from the [template](/docs/templates#agents). Read the repo from `git remote get-url origin` and confirm it with the person. Read the Linear project from the project's own docs if they name it, and confirm it; otherwise ask. Never copy it from another project.
95
+ - Offer the **GitHub repo** and the **Linear project**, both optional, and add each one the person confirms to the Project workflow section of `AGENTS.md`, from the [template](/docs/templates#agents). Read the repo from `git remote get-url origin` and confirm it with the person. Read the Linear project from the project's own docs if they name it, and confirm it; otherwise ask. Never copy it from another project.
68
96
  - Print the [status circles](/docs/Guides/setup#working-with-the-agent) question to the person. If they say yes, copy the Status circles section from the template into Project workflow. Write their answer in `docs/development/coding-standards.md`, under "Details". If `AGENTS.md` already has status circles in the project's own words, keep that.
69
97
 
70
- **How to check:** Project workflow in `AGENTS.md` names the GitHub repo and the Linear project, and `docs/development/coding-standards.md` records whether the project took the status circles.
98
+ **How to check:** Project workflow in `AGENTS.md` names each link the person confirmed, and `docs/development/coding-standards.md` records the answer for each option.
71
99
 
72
100
  **Fixes in 3.0.6.** Never published to npm: these fixes are in 3.0.7. Nothing to do in a project. The update steps gained two rules: when the project's `AGENTS.md` records the standards in its own words, an update writes the changed line in that shape; and after an update the project's list of opted-out and changed standards is re-read, taking off it anything the new version now covers. The 3.0.5 numbers change has its check spelled out: `pnpm lint` reporting a `no-magic-numbers` finding means it is not finished. A project-specific block in an ESLint config is now defined: it is recorded in the project's `docs/development/coding-standards.md`, or `pnpm lint` fails without it.
73
101
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@activatus/code-standards",
3
- "version": "3.0.8",
3
+ "version": "3.1.0",
4
4
  "description": "The Activatus code standards: the rules as Markdown, and the config files to copy. Install it so an AI agent can read the standards from node_modules.",
5
5
  "repository": {
6
6
  "type": "git",
@@ -41,13 +41,13 @@
41
41
 
42
42
  [How this project runs its work. These are the project's own decisions, not part of the code standards. Say where they are written up (usually `docs/development/`), then list the rules an agent must follow:]
43
43
 
44
- - **Who commits**: [whether AI agents may commit, push or make branches, and when]
44
+ - **Who commits**: [whether AI agents may commit, push or make branches, and when. If the person said yes to asking before committing during setup: "Ask the person before every commit and push, and wait for a clear yes to that specific action. A yes covers one action only." If they said no, leave the asking rule out]
45
45
  - **Branches**: [how branches are named]
46
46
  - **Commit messages**: [the commit message format]
47
47
  - **Pull requests**: [review and CI requirements, and where Pull Requests merge to]
48
48
  - **Merging and releases**: [merge strategy, and how work reaches production]
49
- - **GitHub repo**: [https://github.com/organisation/repo, read from the git remote and confirmed with the person]
50
- - **Linear project**: [workspace, project and ticket prefix, such as `activatus-life`, Launchpad, `ACT`, read from the project's docs or asked for, and confirmed with the person. Or "None"]
49
+ - **GitHub repo**: [Optional. https://github.com/organisation/repo, read from the git remote and confirmed with the person. Delete this line if the project does not use it]
50
+ - **Linear project**: [Optional. Workspace, project and ticket prefix, such as `activatus-life`, Launchpad, `ACT`, read from the project's docs or asked for, and confirmed with the person. Delete this line if the project does not use Linear]
51
51
 
52
52
  **Never copy a Linear workspace or ticket prefix from another project.** If the Linear project above is missing, ask before creating, linking or citing any ticket.
53
53