@dypt/cli 0.1.4 → 0.1.5

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/dist/index.js CHANGED
@@ -9,7 +9,7 @@ import { Argument, Command, Option } from "commander";
9
9
  // package.json
10
10
  var package_default = {
11
11
  name: "@dypt/cli",
12
- version: "0.1.4",
12
+ version: "0.1.5",
13
13
  description: "Command-line interface for dypt task management",
14
14
  license: "SEE LICENSE IN LICENSE",
15
15
  homepage: "https://dypt.app",
@@ -434,18 +434,51 @@ dypt agent install claude
434
434
 
435
435
  When working on repo tasks:
436
436
 
437
- - Use the dypt CLI to inspect tasks, notes, children, dependencies, and nearby branch context before changing work.
437
+ - Use the dypt CLI to inspect tasks, notes, children, dependencies, and nearby
438
+ branch context before changing work.
438
439
  - Search before creating new tasks to avoid duplicates.
439
- - If the right parent or scope for a new or moved task is not clear, ask the user to confirm before changing task structure.
440
+ - If the right parent or scope for a new or moved task is not clear from the
441
+ user request, current session, existing dypt hierarchy, or this file, ask the
442
+ user to confirm before changing task structure.
440
443
  - Capture durable context in dypt notes.
441
- - Format longer dypt notes with appropriate markdown so they are readable and well presented.
442
- - When referencing tasks in dypt notes, use dypt task links such as [#123](#task-123) and do not repeat the task title after the link.
443
- - When referring to tasks back to the user, include both id and title, for example #123 Add CLI docs.
444
+ - Format longer dypt notes with appropriate markdown so they are readable and
445
+ well presented.
446
+ - When referencing tasks in dypt notes, use dypt task links such as
447
+ [#123](#task-123) and do not repeat the task title after the link.
448
+ - When referring to tasks back to the user, include both id and title, for
449
+ example #123 Add CLI docs.
444
450
  - Track follow-up work as dypt tasks.
445
451
  - Do not create a parallel markdown TODO tracker.
446
- - Do not set leaf tasks to in progress; dypt derives in progress for parent tasks from child state.
447
- - Preview cleanup or bulk changes before applying them when preview is available.
452
+ - Do not set leaf tasks to in progress; dypt derives in progress for parent
453
+ tasks from child state.
454
+ - Preview cleanup or bulk changes before applying them when preview is
455
+ available.
448
456
  - If the dypt-cli skill is available, use it for dypt task workflows.
457
+
458
+ ## dypt Scope
459
+
460
+ If this repository usually tracks work under a specific dypt branch, name that
461
+ branch here:
462
+
463
+ Use the dypt task branch <branch name or task id> as the default scope for this
464
+ repository.
465
+
466
+ If a task does not clearly belong under that branch, ask before creating or
467
+ moving it.
468
+
469
+ ## Useful Commands
470
+
471
+ \`\`\`bash
472
+ dypt task search "<query>"
473
+ dypt task get <ref>
474
+ dypt task summary <ref>
475
+ dypt task tree <ref> --depth 2
476
+ dypt note get <ref>
477
+ dypt dep list <ref>
478
+ dypt task plan next-actions <ref>
479
+ dypt task plan focus <ref>
480
+ dypt task plan metadata <ref> --leaves-only
481
+ \`\`\`
449
482
  `;
450
483
  function metadataPath(targetPath) {
451
484
  return path3.join(targetPath, METADATA_FILE);