@franshjy/dbrief 0.1.0 → 0.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@franshjy/dbrief",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Extract Codex session activity into daily artifacts",
   "main": "dist/index.js",
   "type": "module",
@@ -17,14 +17,14 @@
     "test": "vitest",
     "typecheck": "tsc --noEmit"
   },
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/franshjy/Dbrief.git"
-  },
-  "publishConfig": {
-    "access": "public"
-  },
-  "keywords": [],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/franshjy/Dbrief.git"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "keywords": [],
   "author": "",
   "license": "AGPL-3.0",
   "bugs": {

package/skills/dbrief-note/SKILL.md

@@ -3,21 +3,21 @@ name: dbrief-note
 description: Generate a polished daily note from a Dbrief JSON artifact. Use when the user asks to create, write, or generate a daily note, daily summary, or project log.
 ---
 
-# Daily Note Generator
-
-Read the Dbrief JSON artifact and generate one portable Markdown daily note.
-Infer note conventions from the target location, existing file, nearby templates, and project instructions, but always produce Markdown.
-
-## Required Workflow
-
-When the user asks for a daily note, first generate or refresh the artifact with the Dbrief CLI before writing the note.
-
-1. Run `dbrief extract` for the requested date or range.
-2. Use `--date`, `--from`, `--to`, or `--out` when the user request needs them.
-3. Read the generated JSON artifact.
-4. Write the final Markdown note from that artifact.
-
-Default artifact names are `./dbrief_YYYY-MM-DD.json` in the current directory unless `--out` is provided.
+# Daily Note Generator
+
+Read the Dbrief JSON artifact and generate one portable Markdown daily note.
+Infer note conventions from the target location, existing file, nearby templates, and project instructions, but always produce Markdown.
+
+## Required Workflow
+
+When the user asks for a daily note, first generate or refresh the artifact with the Dbrief CLI before writing the note.
+
+1. Run `dbrief extract` for the requested date or range.
+2. Use `--date`, `--from`, `--to`, or `--out` when the user request needs them.
+3. Read the generated JSON artifact.
+4. Write the final Markdown note from that artifact.
+
+Default artifact names are `./dbrief_YYYY-MM-DD.json` in the current directory unless `--out` is provided.
 
 ## Output Format
 
@@ -48,15 +48,15 @@ If no stronger existing convention is detected, use this base structure:
 
 ## Instructions
 
-1. If the artifact does not already exist for the requested date, run `dbrief extract` first.
-2. Read the JSON artifact (user provides the path, or use `./dbrief_YYYY-MM-DD.json` from the current directory by default)
-3. For each project, analyze the conversation threads to identify:
-   - Concrete changes (features, fixes, decisions made)
-   - Unresolved items (questions raised, blockers, incomplete work)
-   - Notable context (architectural decisions, trade-offs discussed)
-4. Write a concise summary that ties everything together
-5. Keep the tone retrospective and factual
-6. Use the project directory name as the project heading
+1. If the artifact does not already exist for the requested date, run `dbrief extract` first.
+2. Read the JSON artifact (user provides the path, or use `./dbrief_YYYY-MM-DD.json` from the current directory by default)
+3. For each project, analyze the conversation threads to identify:
+   - Concrete changes (features, fixes, decisions made)
+   - Unresolved items (questions raised, blockers, incomplete work)
+   - Notable context (architectural decisions, trade-offs discussed)
+4. Write a concise summary that ties everything together
+5. Keep the tone retrospective and factual
+6. Use the project directory name as the project heading
 
 ## Writer Rules