@codemation/agent-skills 0.1.0 → 0.1.3

package/CHANGELOG.md

@@ -1,5 +1,25 @@
 # @codemation/agent-skills
 
+## 0.1.3
+
+### Patch Changes
+
+- [#41](https://github.com/MadeRelevant/codemation/pull/41) [`a72444e`](https://github.com/MadeRelevant/codemation/commit/a72444e25c4e744a9a90e231a59c93f8d90346e5) Thanks [@cblokland90](https://github.com/cblokland90)! - Add `WorkflowTestKit` and related engine test harness exports on `@codemation/core/testing`, with create-codemation templates and agent skills updated to document plugin unit tests.
+
+## 0.1.2
+
+### Patch Changes
+
+- [#39](https://github.com/MadeRelevant/codemation/pull/39) [`cbfe843`](https://github.com/MadeRelevant/codemation/commit/cbfe843ef2363e400a219f4d0bcd05b091ab83b4) Thanks [@cblokland90](https://github.com/cblokland90)! - Add `WorkflowTestKit` and related engine test harness exports on `@codemation/core/testing`, with create-codemation templates and agent skills updated to document plugin unit tests.
+
+## 0.1.1
+
+### Patch Changes
+
+- [#35](https://github.com/MadeRelevant/codemation/pull/35) [`75b885b`](https://github.com/MadeRelevant/codemation/commit/75b885b111cc34ffe3a192ca9cc8cd3864fdf8ff) Thanks [@cblokland90](https://github.com/cblokland90)! - Replace the local-development `pglite` path with SQLite across the host, CLI, scaffolding templates, and packaged dev flows while keeping PostgreSQL for production-aligned and shared integration scenarios.
+
+  Split Prisma into provider-specific PostgreSQL and SQLite schema and migration tracks so generated clients and startup migrations select the correct backend without the old `pglite` socket adapter.
+
 ## 0.1.0
 
 ### Minor Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codemation/agent-skills",
-  "version": "0.1.0",
+  "version": "0.1.3",
   "description": "Reusable agent skills for Codemation projects and plugin development.",
   "publishConfig": {
     "access": "public"
@@ -17,9 +17,6 @@
   "bin": {
     "codemation-agent-skills": "./bin/codemation-agent-skills.mjs"
   },
-  "scripts": {
-    "test": "vitest run"
-  },
   "keywords": [
     "codemation",
     "agent",
@@ -38,5 +35,8 @@
     "CHANGELOG.md",
     "bin",
     "skills"
-  ]
-}
+  ],
+  "scripts": {
+    "test": "vitest run"
+  }
+}

package/skills/codemation-cli/SKILL.md

@@ -33,7 +33,7 @@ Do not use this skill for workflow graph design, custom node implementation, or
 1. Treat `codemation.config.ts` as the consumer entrypoint.
 2. Mention `.codemation/output` only when build artifacts or runtime bootstrap details matter.
 3. When the user is in the monorepo, distinguish framework-author mode from normal consumer mode explicitly.
-4. When Redis-backed execution is involved, mention the shared PostgreSQL requirement instead of assuming PGlite still fits.
+4. When Redis-backed execution is involved, mention the shared PostgreSQL requirement instead of assuming local SQLite still fits.
 
 ## Read next when needed
 

package/skills/codemation-cli/references/command-map.md

@@ -57,6 +57,6 @@ Use `codemation dev --watch-framework` when working inside the Codemation monore
 
 ## Environment notes
 
-- PGlite is the zero-setup default for starter apps.
-- When `REDIS_URL` is set, use a shared PostgreSQL `DATABASE_URL`; BullMQ cannot run on PGlite.
+- SQLite is the zero-setup default for starter apps.
+- When `REDIS_URL` is set, use a shared PostgreSQL `DATABASE_URL`; BullMQ cannot run on SQLite.
 - Use `--consumer-root` when commands need to target a different consumer app root.

package/skills/codemation-custom-node-development/SKILL.md

@@ -27,6 +27,10 @@ Do not use this skill for pure workflow chaining questions unless the node imple
 4. Remember that runtime execution receives batches of items.
 5. Drop to class-based node APIs only when you need constructor-injected collaborators, decorators, or deeper runtime metadata.
 
+## Testing with `WorkflowTestKit`
+
+For engine-backed tests without the host, use **`WorkflowTestKit`** from **`@codemation/core/testing`**: **`registerDefinedNodes([...])`**, then **`runNode`** or **`run`**. See the plugin development doc and `@codemation/core` tests for examples.
+
 ## Read next when needed
 
 - Read `references/node-patterns.md` for `defineNode(...)` patterns and packaging guidance.

package/skills/codemation-framework-concepts/references/architecture-map.md

@@ -22,7 +22,7 @@ Use the minimum setup when:
 
 - you are starting a new app
 - one process is enough
-- local PGlite is fine
+- local SQLite is fine
 - fast local iteration matters more than shared worker infrastructure
 
 ## Production setup
@@ -36,7 +36,7 @@ Move to the production shape when:
 
 That usually means:
 
-- PostgreSQL instead of embedded PGlite
+- PostgreSQL instead of local SQLite
 - Redis for queue-backed execution
 - BullMQ-backed scheduling
 

package/skills/codemation-plugin-development/SKILL.md

@@ -32,6 +32,11 @@ Do not use this skill for ordinary consumer workflow-only changes unless the wor
 - `src/nodes/*`: custom node definitions
 - `src/credentialTypes/*`: custom credential definitions
 - `src/index.ts`: package exports
+- `test/*.test.ts` (optional): Vitest + `WorkflowTestKit` from `@codemation/core/testing` for engine-backed unit tests without starting the full host (`pnpm test`)
+
+## Unit tests (`WorkflowTestKit`)
+
+Import **`WorkflowTestKit`** from **`@codemation/core/testing`**. Use **`registerDefinedNodes([...])`** for `defineNode` packages, then **`runNode({ node: yourNode.create(...), items })`** or **`run({ workflow, items })`** for fuller graphs. Prefer this for fast node tests; use **`codemation dev:plugin`** when you need the UI and persistence.
 
 ## Read next when needed