codiedev 0.5.0 → 0.5.1

package/dist/cli.js

@@ -62,15 +62,26 @@ Other:
   codiedev docs                          Print the full usage guide
   codiedev version                       Show version
 
-Filename conventions:
-  spec-*.md      → spec          review-*.md    → review
-  decision-*.md  → decision      proposal-*.md  → proposal
-  bugfix-*.md    → bugfix        anything else  → note
+The 90% workflow:
+  1. Name your file 'spec-<topic>.md' and push.
+  2. Ping a teammate to pull review.
+  3. They edit, push back. Versions stack. Done.
+
+Other artifact types (rare — use the matching prefix):
+  review-*.md → review     decision-*.md → decision
+  proposal-*.md → proposal  bugfix-*.md → bugfix
+  anything else → note
+
+Skills (slash commands):
+  Add 'name:' + 'description:' YAML frontmatter to any pushed file
+  and it shows up as /<name> in Claude Code / Codex. Filename
+  prefix doesn't matter — frontmatter is the signal.
 
 Examples:
-  codiedev push docs/specs/spec-cart-clear.md
+  codiedev push spec-cart-clear.md          # the typical case
+  codiedev push portal-design.md            # with name:/description: → skill
   codiedev pull spec-cart-clear.md
-  codiedev ping maya "thoughts on batch vs parallel?" --with spec-cart-clear.md
+  codiedev ping maya "thoughts?" --with spec-cart-clear.md
   codiedev inbox --unread
   codiedev note "idempotency key is worth a follow-up"
 
@@ -96,17 +107,23 @@ codiedev connect — link your agent CLI to CodieDev
     push: `
 codiedev push — author or update an artifact
 
-  Usage:
-    codiedev push <file.md> [--type spec|review|decision|proposal|bugfix|note]
+  Default path:
+    codiedev push spec-<topic>.md
 
-  The file's basename becomes its key (unique per company). Pushing the
-  same key again creates a new version — full history is preserved.
+  The file's basename becomes its key (unique per company). Pushing
+  the same key again versions it — full history is preserved.
 
-  Type is inferred from the filename prefix unless you override with --type.
+  Other types: rename with the matching prefix (review-*, decision-*,
+  proposal-*, bugfix-*) or pass --type. Anything else lands as 'note'.
+
+  Skills (slash commands): add 'name:' + 'description:' YAML
+  frontmatter to the top of the file. It shows up as /<name> in
+  the Skills tab. Filename prefix doesn't matter for the skill role.
 
   Examples:
-    codiedev push spec-cart-clear.md
-    codiedev push docs/review-auth.md --type review
+    codiedev push spec-cart-clear.md            # the typical case
+    codiedev push portal-design.md              # with name:/description: → skill
+    codiedev push docs/review-auth.md
     codiedev push notes/random.md --type note
 `.trim(),
     pull: `
@@ -244,6 +261,25 @@ Artifacts have a status that auto-advances as PRs reference them:
 Artifacts stay editable at every stage, including after merge —
 lessons-learned and follow-up notes append as new versions.
 
+## Skills
+
+Default path:
+
+    1. Pick a name: e.g. portal-design
+    2. Top the file with frontmatter:
+         ---
+         name: portal-design
+         description: Use when reviewing or building portal UI.
+         ---
+         # body...
+    3. codiedev push portal-design.md
+
+It's now /portal-design in Claude Code / Codex.
+
+Filename prefix is irrelevant for skills — frontmatter is the only
+signal. The stored artifact type still follows the filename rule
+(so a skill in a spec file is both a 'spec' and a callable skill).
+
 ## Portal
 
 Everything you do in the CLI is visible at:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codiedev",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "Connect Claude Code or Codex to CodieDev for org-wide session capture and artifact collaboration",
   "bin": {
     "codiedev": "./dist/cli.js",