@staff0rd/assist 0.147.1 → 0.147.2

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.
@@ -51,7 +51,7 @@ Use a behavioural, BDD-style structure:
51
51
 
52
52
  - **Outer `describe`** — the function or module under test
53
53
  - **Inner `describe("when ...")`** — groups tests that share the same setup/scenario
54
- - **`it("should ...")`** — asserts a single rule or behaviour
54
+ - **`it("should ...")`** — asserts a single rule or behaviour. State specifiers (flags, syntax variants, conditions) belong in `when` blocks, never in `it` descriptions — keep assertions as bare outcomes (e.g. "should allow", "should reject")
55
55
 
56
56
  Each test follows an **Arrange, Act, Assert** pattern. Do NOT add `// arrange`, `// act`, `// assert` comments — just structure the code in that order with whitespace separating the three sections.
57
57
 
@@ -35,7 +35,7 @@ Assess each test file against these criteria:
35
35
  ### BDD structure and Arrange-Act-Assert
36
36
  - Does the outer `describe` name the function or module under test?
37
37
  - Do inner `describe("when ...")` blocks group tests by shared setup/scenario?
38
- - Do `it` blocks use `should` phrasing (e.g., `it("should return empty array when no matches")`)?
38
+ - Do `it` blocks use `should` phrasing with bare outcomes (e.g., `it("should allow")`, `it("should reject")`)? State specifiers (flags, syntax variants, conditions) belong in `when` blocks, never in `it` descriptions.
39
39
  - Does each test follow Arrange, Act, Assert ordering (without comments labelling the sections)?
40
40
  - Are assertions minimal per test — ideally one, at most two closely related? If multiple things are asserted about the same action, are they split into separate `it` blocks under the same `describe("when ...")`?
41
41
 
package/dist/index.js CHANGED
@@ -6,7 +6,7 @@ import { Command } from "commander";
6
6
  // package.json
7
7
  var package_default = {
8
8
  name: "@staff0rd/assist",
9
- version: "0.147.1",
9
+ version: "0.147.2",
10
10
  type: "module",
11
11
  main: "dist/index.js",
12
12
  bin: {
@@ -10276,7 +10276,7 @@ import { fileURLToPath as fileURLToPath7 } from "url";
10276
10276
  import * as fs23 from "fs";
10277
10277
  import * as path45 from "path";
10278
10278
  import chalk105 from "chalk";
10279
- async function syncClaudeMd(claudeDir, targetBase) {
10279
+ async function syncClaudeMd(claudeDir, targetBase, options2) {
10280
10280
  const source = path45.join(claudeDir, "CLAUDE.md");
10281
10281
  const target = path45.join(targetBase, "CLAUDE.md");
10282
10282
  const sourceContent = fs23.readFileSync(source, "utf-8");
@@ -10288,7 +10288,7 @@ async function syncClaudeMd(claudeDir, targetBase) {
10288
10288
  );
10289
10289
  console.log();
10290
10290
  printDiff(targetContent, sourceContent);
10291
- const confirm = await promptConfirm(
10291
+ const confirm = options2?.yes || await promptConfirm(
10292
10292
  chalk105.red("Overwrite existing CLAUDE.md?"),
10293
10293
  false
10294
10294
  );
@@ -10350,7 +10350,7 @@ async function sync(options2) {
10350
10350
  const targetBase = path47.join(os.homedir(), ".claude");
10351
10351
  syncCommands(claudeDir, targetBase);
10352
10352
  await syncSettings(claudeDir, targetBase, { yes: options2?.yes });
10353
- await syncClaudeMd(claudeDir, targetBase);
10353
+ await syncClaudeMd(claudeDir, targetBase, { yes: options2?.yes });
10354
10354
  }
10355
10355
  function syncCommands(claudeDir, targetBase) {
10356
10356
  const sourceDir = path47.join(claudeDir, "commands");
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@staff0rd/assist",
3
- "version": "0.147.1",
3
+ "version": "0.147.2",
4
4
  "type": "module",
5
5
  "main": "dist/index.js",
6
6
  "bin": {