tape-six 1.7.9 → 1.7.10

package/README.md

@@ -110,6 +110,7 @@ tape-six/
 ├── src/              # Source code (test engine, reporters, runners, utilities)
 ├── web-app/          # Browser test UI application
 ├── tests/            # Test files (JS + TS)
+├── skills/           # Agent Skills (agentskills.io) shipped via npm
 ├── wiki/             # GitHub wiki documentation (submodule)
 └── vendors/          # Git submodules (deep6)
 ```
@@ -131,9 +132,8 @@ The whole API is based on two objects: `test` and `Tester`.
 import test from 'tape-six';
 // import {test} from 'tape-six';
 
-// CommonJS:
+// CommonJS (named import is recommended):
 // const {test} = require('tape-six');
-// const {default: test} = require('tape-six');
 ```
 
 To help port tests from other frameworks, `test()` is aliased as `suite()`, `describe()` and `it()`. When called inside a test body, `test()` and its aliases automatically delegate to the current tester's `t.test()` method. The same applies to `test.skip()`, `test.todo()`, and `test.asPromise()`. Using `t.test()` directly is still preferred because it makes the delegation explicit.
@@ -419,6 +419,7 @@ Test output can be controlled by flags. See [Supported flags](https://github.com
 
 The most recent releases:
 
+- 1.7.10 _Switched from workflows to Agent Skills (agentskills.io) for consumer integration. Improved CJS import docs._
 - 1.7.9 _Merged test directories, fixed `.d.ts` typings, added `ts-check` to CI._
 - 1.7.8 _Bug fix: Deno stdout flush before exit to prevent truncated output._
 - 1.7.7 _Bug fix: Windows path normalization in `tape6-server`, documented `--flags=FO` option form._

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tape-six",
-  "version": "1.7.9",
+  "version": "1.7.10",
   "description": "TAP-based unit test library for Node, Deno, Bun, and browsers. ES modules, TypeScript, zero dependencies.",
   "type": "module",
   "main": "index.js",
@@ -81,7 +81,7 @@
     "llms.txt",
     "llms-full.txt",
     "TESTING.md",
-    "workflows"
+    "skills"
   ],
   "tape6": {
     "tests": [
@@ -104,10 +104,10 @@
   },
   "devDependencies": {
     "@types/chai": "^5.2.3",
-    "@types/node": "^25.3.3",
+    "@types/node": "^25.3.5",
     "chai": "^6.2.2",
     "playwright": "^1.58.2",
-    "puppeteer": "^24.37.5",
+    "puppeteer": "^24.38.0",
     "typescript": "^5.9.3"
   }
 }

package/{workflows/write-tests.md → skills/write-tests/SKILL.md}

@@ -1,5 +1,6 @@
 ---
-description: Write or update tape-six tests for a module or feature
+name: write-tests
+description: Write or update tests using the tape-six testing library. Use when asked to write tests, add test coverage, or create test files for a project that uses tape-six.
 ---
 
 # Write Tests
@@ -17,7 +18,7 @@ Write or update tests using the tape-six testing library.
 1. Read the testing guide at `node_modules/tape-six/TESTING.md` for API reference and patterns.
 2. Identify the module or feature to test. Read its source code to understand the public API.
 3. Create or update the test file in `tests/test-<name>.js` (or `.ts` for TypeScript projects):
-   - Import `test` from `tape-six` (ESM: `import test from 'tape-six'`; CJS: `const {test} = require('tape-six')`).
+   - Import `test` from `tape-six` (ESM: `import test from 'tape-six'`; CJS: `const {test} = require('tape-six')` — named import is recommended for CommonJS).
    - Import the module under test using the project's package name.
    - Write one top-level `test()` per logical group.
    - Use embedded `await t.test()` for sub-cases.
@@ -25,9 +26,7 @@ Write or update tests using the tape-six testing library.
    - Cover: normal operation, edge cases, error conditions.
    - Use `t.equal` for primitives, `t.deepEqual` for objects/arrays, `t.throws` for errors, `await t.rejects` for async errors.
    - All `msg` arguments are optional but recommended for clarity.
-   // turbo
 4. Run the new test file directly to verify: `node tests/test-<name>.js`
-   // turbo
 5. Run the full test suite to check for regressions: `npm test`
    - If debugging, use `npm run test:seq` (runs sequentially, easier to trace issues).
 6. Report results and any failures.