wormclaude 1.0.12 → 1.0.13

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.
Files changed (42) hide show
  1. package/dist/cli.js +12 -1
  2. package/dist/extensions.js +137 -0
  3. package/dist/theme.js +1 -1
  4. package/dist/tools.js +4 -1
  5. package/extensions/code-review/README.md +22 -0
  6. package/extensions/code-review/commands/review/best-practices.toml +15 -0
  7. package/extensions/code-review/commands/review/performance.toml +14 -0
  8. package/extensions/code-review/commands/review/security.toml +16 -0
  9. package/extensions/code-review/wormclaude-extension.json +6 -0
  10. package/extensions/conductor/README.md +250 -0
  11. package/extensions/conductor/commands/conductor/implement.toml +15 -0
  12. package/extensions/conductor/commands/conductor/newTrack.toml +16 -0
  13. package/extensions/conductor/commands/conductor/revert.toml +14 -0
  14. package/extensions/conductor/commands/conductor/setup.toml +16 -0
  15. package/extensions/conductor/commands/conductor/status.toml +15 -0
  16. package/extensions/conductor/templates/.wormclaudeignore +37 -0
  17. package/extensions/conductor/templates/code_styleguides/go.md +48 -0
  18. package/extensions/conductor/templates/code_styleguides/html-css.md +49 -0
  19. package/extensions/conductor/templates/code_styleguides/javascript.md +51 -0
  20. package/extensions/conductor/templates/code_styleguides/python.md +37 -0
  21. package/extensions/conductor/templates/code_styleguides/typescript.md +43 -0
  22. package/extensions/conductor/templates/general.md +23 -0
  23. package/extensions/conductor/templates/plan.md +18 -0
  24. package/extensions/conductor/templates/product-guidelines.md +25 -0
  25. package/extensions/conductor/templates/product.md +21 -0
  26. package/extensions/conductor/templates/tech-stack.md +25 -0
  27. package/extensions/conductor/templates/workflow.md +138 -0
  28. package/extensions/conductor/wormclaude-extension.json +6 -0
  29. package/extensions/git-helper/README.md +16 -0
  30. package/extensions/git-helper/commands/git/branch-cleanup.toml +13 -0
  31. package/extensions/git-helper/commands/git/smart-commit.toml +13 -0
  32. package/extensions/git-helper/wormclaude-extension.json +6 -0
  33. package/extensions/greet/README.md +76 -0
  34. package/extensions/greet/commands/greet.toml +4 -0
  35. package/extensions/greet/wormclaude-extension.json +6 -0
  36. package/extensions/registry.json +52 -0
  37. package/extensions/test-generator/README.md +22 -0
  38. package/extensions/test-generator/commands/test/coverage.toml +12 -0
  39. package/extensions/test-generator/commands/test/integration.toml +13 -0
  40. package/extensions/test-generator/commands/test/unit.toml +13 -0
  41. package/extensions/test-generator/wormclaude-extension.json +6 -0
  42. package/package.json +3 -2
@@ -0,0 +1,52 @@
1
+ {
2
+ "extensions": [
3
+ {
4
+ "name": "conductor",
5
+ "version": "1.0.0",
6
+ "description": "Context-Driven Development: spec-driven planning, TDD workflow, and execution tracking.",
7
+ "category": "productivity",
8
+ "author": "WormClaude Team",
9
+ "path": "./conductor"
10
+ },
11
+ {
12
+ "name": "git-helper",
13
+ "version": "1.0.0",
14
+ "description": "Git workflow automation: smart conventional commits and branch cleanup.",
15
+ "category": "productivity",
16
+ "author": "WormClaude Team",
17
+ "path": "./git-helper"
18
+ },
19
+ {
20
+ "name": "code-review",
21
+ "version": "1.0.0",
22
+ "description": "Automated code review: security, performance, and best-practices passes.",
23
+ "category": "quality",
24
+ "author": "WormClaude Team",
25
+ "path": "./code-review"
26
+ },
27
+ {
28
+ "name": "test-generator",
29
+ "version": "1.0.0",
30
+ "description": "Generate unit and integration tests and analyze coverage gaps.",
31
+ "category": "testing",
32
+ "author": "WormClaude Team",
33
+ "path": "./test-generator"
34
+ },
35
+ {
36
+ "name": "exclude-tools",
37
+ "version": "1.0.0",
38
+ "description": "Example extension that disables specific tools for a restricted environment.",
39
+ "category": "other",
40
+ "author": "WormClaude Team",
41
+ "path": "./exclude-tools"
42
+ },
43
+ {
44
+ "name": "greet",
45
+ "version": "1.0.0",
46
+ "description": "A simple greeting command — minimal example extension.",
47
+ "category": "fun",
48
+ "author": "WormClaude Team",
49
+ "path": "./greet"
50
+ }
51
+ ]
52
+ }
@@ -0,0 +1,22 @@
1
+ # Test Generator Extension
2
+
3
+ Automatically generate tests and analyze coverage for your code.
4
+
5
+ ## Commands
6
+
7
+ - `/test:unit` - Generate unit tests for the current file or a named function
8
+ - `/test:integration` - Generate integration tests for a flow, endpoint, or module boundary
9
+ - `/test:coverage` - Analyze coverage and generate tests for the biggest gaps
10
+
11
+ ## Installation
12
+
13
+ ```
14
+ wormclaude extensions install --from-registry test-generator
15
+ ```
16
+
17
+ Or use `/browse-extensions` in the CLI and select this extension.
18
+
19
+ ## Notes
20
+
21
+ - Tests are written to match the project's existing framework and conventions (Jest/Vitest/pytest/go test/JUnit…) — never assumed.
22
+ - Generated tests are real and runnable; the command runs them and fixes failures before reporting.
@@ -0,0 +1,12 @@
1
+ description = "Analyze test coverage and generate tests for the biggest gaps"
2
+ prompt = """
3
+ Analyze test coverage and close the most important gaps.
4
+
5
+ Steps:
6
+ 1. Find and run the project's coverage command (from README/manifest/config, e.g. `npm test -- --coverage`, `pytest --cov`, `go test -cover`). If there is no coverage tooling, say so and estimate gaps by reading the code and existing tests instead.
7
+ 2. Identify the least-covered, highest-risk areas — prioritize core logic, error handling, and edge cases over trivial getters/config.
8
+ 3. Propose a short, ranked list of the gaps worth covering and why.
9
+ 4. For the top gaps, generate real unit/integration tests following the project's framework and conventions (Write the files), then re-run tests/coverage and report the improvement.
10
+
11
+ Focus on meaningful coverage of real behavior — do not chase a coverage number with shallow tests.
12
+ """
@@ -0,0 +1,13 @@
1
+ description = "Generate integration tests for a flow, endpoint, or module boundary"
2
+ prompt = """
3
+ Generate integration tests for the flow or boundary the user names (e.g. an API endpoint, a service + its DB, a multi-component flow).
4
+
5
+ Steps:
6
+ 1. Map the flow: identify the entry point, the components/services involved, and the external systems (DB, queue, third-party API).
7
+ 2. Detect the project's integration-test setup (test framework, fixtures, test DB, HTTP client like Supertest/requests/httptest). Match existing patterns; never assume.
8
+ 3. Write tests that exercise the COMPLETE flow end-to-end, not units in isolation: real (or test-double) wiring, auth/authorization, DB transactions, and form/API submissions. Cover success and key failure scenarios.
9
+ 4. Set up and tear down test state properly (fixtures, transactions, cleanup) so tests are isolated and repeatable.
10
+ 5. Create the test file(s) with Write, run them, and confirm they pass.
11
+
12
+ If the project has no integration-test harness yet, scaffold a minimal one following the project's stack, and say what you added.
13
+ """
@@ -0,0 +1,13 @@
1
+ description = "Generate unit tests for the current file or a named function/path"
2
+ prompt = """
3
+ Generate unit tests for the target the user names (a file, function, or path). If none is named, ask which file to cover, then proceed.
4
+
5
+ Steps:
6
+ 1. Read the target code and understand its behavior, inputs, outputs, and side effects.
7
+ 2. Detect the project's test framework and conventions by examining existing test files, the package manifest, and config (Jest/Vitest/pytest/go test/JUnit…). NEVER assume — match what the project already uses, including file naming and folder location.
8
+ 3. Write tests that cover: the happy path, important edge cases, and failure/error paths. Mock external dependencies (network, DB, filesystem) as the project does.
9
+ 4. Create the test file with Write using the project's naming convention, then run the test command and confirm the new tests pass (fix them if they don't).
10
+ 5. Report which behaviors are now covered and any that still need attention.
11
+
12
+ Write real, runnable tests — not placeholders.
13
+ """
@@ -0,0 +1,6 @@
1
+ {
2
+ "name": "test-generator",
3
+ "version": "1.0.0",
4
+ "description": "Generate unit and integration tests and analyze coverage gaps.",
5
+ "contextFileName": "README.md"
6
+ }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "wormclaude",
3
- "version": "1.0.12",
3
+ "version": "1.0.13",
4
4
  "description": "WormClaude CLI - uncensored security+code assistant (ink TUI, Claude-style)",
5
5
  "type": "module",
6
6
  "bin": {
@@ -8,7 +8,7 @@
8
8
  },
9
9
  "scripts": {
10
10
  "dev": "tsx src/cli.tsx",
11
- "build": "tsc && node scripts/copy-skills.mjs",
11
+ "build": "tsc && node scripts/copy-skills.mjs && node scripts/copy-extensions.mjs",
12
12
  "start": "node dist/cli.js",
13
13
  "prepublishOnly": "npm run build"
14
14
  },
@@ -28,6 +28,7 @@
28
28
  "files": [
29
29
  "dist",
30
30
  "skills",
31
+ "extensions",
31
32
  "README.md"
32
33
  ],
33
34
  "engines": {