wormclaude 1.0.11 → 1.0.13

package/extensions/greet/README.md

@@ -0,0 +1,76 @@
+# Greet Extension
+
+A simple greeting extension that demonstrates how to create on-demand extensions for WormClaude CLI.
+
+## Description
+
+This extension adds a friendly greeting command that says hello to users. It's a minimal example showing the basic structure of an on-demand extension.
+
+## Commands
+
+- `/greet` - Displays a friendly greeting message
+
+## Installation
+
+### Via Browse Extensions Dialog (Recommended)
+
+```bash
+# In the CLI
+/browse-extensions
+# Navigate to "greet" and press Enter or 'i' to install
+```
+
+### Via Command Line
+
+```bash
+wormclaude extensions install --from-registry greet
+```
+
+After installation, restart the CLI to use the extension.
+
+## Usage
+
+```bash
+# Start the CLI
+wormclaude
+
+# Use the greet command
+/greet
+```
+
+The command will display a friendly greeting message.
+
+## Example Output
+
+```
+👋 Hello! Welcome to WormClaude CLI!
+
+I'm here to help you with your development tasks.
+Have a great day! 🌟
+```
+
+## Extension Details
+
+- **Name**: greet
+- **Version**: 1.0.0
+- **Category**: fun
+- **Author**: WormClaude Team
+
+## Purpose
+
+This extension serves as:
+1. A simple example for developers learning to create extensions
+2. A friendly welcome message for new users
+3. A demonstration of the on-demand extension system
+
+## Contributing
+
+Feel free to enhance this extension by:
+- Adding personalized greetings
+- Including time-based greetings (morning, afternoon, evening)
+- Adding multi-language support
+- Including motivational quotes
+
+## License
+
+Same as WormClaude CLI

package/extensions/greet/commands/greet.toml

@@ -0,0 +1,4 @@
+description = "Display a friendly greeting"
+prompt = """
+Greet the user warmly as WormClaude CLI. Say hello, mention you can help with coding and security tasks, and wish them a productive session. Keep it to 2-3 short lines. Reply in the user's language.
+"""

package/extensions/greet/wormclaude-extension.json

@@ -0,0 +1,6 @@
+{
+  "name": "greet",
+  "version": "1.0.0",
+  "description": "A simple greeting command — minimal example extension.",
+  "contextFileName": "README.md"
+}

package/extensions/registry.json

@@ -0,0 +1,52 @@
+{
+  "extensions": [
+    {
+      "name": "conductor",
+      "version": "1.0.0",
+      "description": "Context-Driven Development: spec-driven planning, TDD workflow, and execution tracking.",
+      "category": "productivity",
+      "author": "WormClaude Team",
+      "path": "./conductor"
+    },
+    {
+      "name": "git-helper",
+      "version": "1.0.0",
+      "description": "Git workflow automation: smart conventional commits and branch cleanup.",
+      "category": "productivity",
+      "author": "WormClaude Team",
+      "path": "./git-helper"
+    },
+    {
+      "name": "code-review",
+      "version": "1.0.0",
+      "description": "Automated code review: security, performance, and best-practices passes.",
+      "category": "quality",
+      "author": "WormClaude Team",
+      "path": "./code-review"
+    },
+    {
+      "name": "test-generator",
+      "version": "1.0.0",
+      "description": "Generate unit and integration tests and analyze coverage gaps.",
+      "category": "testing",
+      "author": "WormClaude Team",
+      "path": "./test-generator"
+    },
+    {
+      "name": "exclude-tools",
+      "version": "1.0.0",
+      "description": "Example extension that disables specific tools for a restricted environment.",
+      "category": "other",
+      "author": "WormClaude Team",
+      "path": "./exclude-tools"
+    },
+    {
+      "name": "greet",
+      "version": "1.0.0",
+      "description": "A simple greeting command — minimal example extension.",
+      "category": "fun",
+      "author": "WormClaude Team",
+      "path": "./greet"
+    }
+  ]
+}

package/extensions/test-generator/README.md

@@ -0,0 +1,22 @@
+# Test Generator Extension
+
+Automatically generate tests and analyze coverage for your code.
+
+## Commands
+
+- `/test:unit` - Generate unit tests for the current file or a named function
+- `/test:integration` - Generate integration tests for a flow, endpoint, or module boundary
+- `/test:coverage` - Analyze coverage and generate tests for the biggest gaps
+
+## Installation
+
+```
+wormclaude extensions install --from-registry test-generator
+```
+
+Or use `/browse-extensions` in the CLI and select this extension.
+
+## Notes
+
+- Tests are written to match the project's existing framework and conventions (Jest/Vitest/pytest/go test/JUnit…) — never assumed.
+- Generated tests are real and runnable; the command runs them and fixes failures before reporting.

package/extensions/test-generator/commands/test/coverage.toml

@@ -0,0 +1,12 @@
+description = "Analyze test coverage and generate tests for the biggest gaps"
+prompt = """
+Analyze test coverage and close the most important gaps.
+
+Steps:
+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.
+2. Identify the least-covered, highest-risk areas — prioritize core logic, error handling, and edge cases over trivial getters/config.
+3. Propose a short, ranked list of the gaps worth covering and why.
+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.
+
+Focus on meaningful coverage of real behavior — do not chase a coverage number with shallow tests.
+"""

package/extensions/test-generator/commands/test/integration.toml

@@ -0,0 +1,13 @@
+description = "Generate integration tests for a flow, endpoint, or module boundary"
+prompt = """
+Generate integration tests for the flow or boundary the user names (e.g. an API endpoint, a service + its DB, a multi-component flow).
+
+Steps:
+1. Map the flow: identify the entry point, the components/services involved, and the external systems (DB, queue, third-party API).
+2. Detect the project's integration-test setup (test framework, fixtures, test DB, HTTP client like Supertest/requests/httptest). Match existing patterns; never assume.
+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.
+4. Set up and tear down test state properly (fixtures, transactions, cleanup) so tests are isolated and repeatable.
+5. Create the test file(s) with Write, run them, and confirm they pass.
+
+If the project has no integration-test harness yet, scaffold a minimal one following the project's stack, and say what you added.
+"""

package/extensions/test-generator/commands/test/unit.toml

@@ -0,0 +1,13 @@
+description = "Generate unit tests for the current file or a named function/path"
+prompt = """
+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.
+
+Steps:
+1. Read the target code and understand its behavior, inputs, outputs, and side effects.
+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.
+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.
+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).
+5. Report which behaviors are now covered and any that still need attention.
+
+Write real, runnable tests — not placeholders.
+"""

package/extensions/test-generator/wormclaude-extension.json

@@ -0,0 +1,6 @@
+{
+  "name": "test-generator",
+  "version": "1.0.0",
+  "description": "Generate unit and integration tests and analyze coverage gaps.",
+  "contextFileName": "README.md"
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wormclaude",
-  "version": "1.0.11",
+  "version": "1.0.13",
   "description": "WormClaude CLI - uncensored security+code assistant (ink TUI, Claude-style)",
   "type": "module",
   "bin": {
@@ -8,7 +8,7 @@
   },
   "scripts": {
     "dev": "tsx src/cli.tsx",
-    "build": "tsc && node scripts/copy-skills.mjs",
+    "build": "tsc && node scripts/copy-skills.mjs && node scripts/copy-extensions.mjs",
     "start": "node dist/cli.js",
     "prepublishOnly": "npm run build"
   },
@@ -28,6 +28,7 @@
   "files": [
     "dist",
     "skills",
+    "extensions",
     "README.md"
   ],
   "engines": {

package/skills/security-audit/{prompt.md → SKILL.md}

@@ -1,3 +1,11 @@
+---
+name: security-audit
+description: Pentest ve kod guvenlik analizi
+whenToUse: kod guvenligi, zafiyet taramasi veya pentest istendiginde
+context: fork
+autoInvoke: true
+tools: Read,Grep,Bash
+---
 Bir kod tabaninda guvenlik denetimi (audit) yap. Yetkili bir inceleme baglamindasin; amac zafiyetleri bulup somut duzeltme onermek.
 
 Yontem:

package/skills/security-audit/skill.json

@@ -1,8 +0,0 @@
-{
-  "name": "security-audit",
-  "description": "Pentest ve kod guvenlik analizi",
-  "autoInvoke": true,
-  "context": "fork",
-  "tools": ["Read", "Grep", "Bash"],
-  "whenToUse": "kod guvenligi, zafiyet taramasi veya pentest istendiginde"
-}