generator-agent 1.0.7 → 1.0.8

package/.vscode/extensions.json

@@ -0,0 +1,8 @@
+{
+	// See https://go.microsoft.com/fwlink/?LinkId=733558
+	// for the documentation about the extensions.json format
+	"recommendations": [
+		"dbaeumer.vscode-eslint",
+		"ms-vscode.extension-test-runner"
+	]
+}

package/.vscode/launch.json

@@ -0,0 +1,17 @@
+// A launch configuration that launches the extension inside a new window
+// Use IntelliSense to learn about possible attributes.
+// Hover to view descriptions of existing attributes.
+// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
+{
+	"version": "0.2.0",
+	"configurations": [
+		{
+			"name": "Run Extension",
+			"type": "extensionHost",
+			"request": "launch",
+			"args": [
+				"--extensionDevelopmentPath=${workspaceFolder}"
+			]
+		}
+	]
+}

package/.vscode-test.mjs

@@ -0,0 +1,5 @@
+import { defineConfig } from '@vscode/test-cli';
+
+export default defineConfig({
+	files: 'test/**/*.test.js',
+});

package/.vscodeignore

@@ -0,0 +1,10 @@
+.vscode/**
+.vscode-test/**
+test/**
+.gitignore
+.yarnrc
+vsc-extension-quickstart.md
+**/jsconfig.json
+**/*.map
+**/eslint.config.mjs
+**/.vscode-test.*

package/CHANGELOG.md

@@ -0,0 +1,9 @@
+# Change Log
+
+All notable changes to the "generator" extension will be documented in this file.
+
+Check [Keep a Changelog](http://keepachangelog.com/) for recommendations on how to structure this file.
+
+## [Unreleased]
+
+- Initial release

package/README.md

@@ -1,59 +1,65 @@
-# Generator Agent for GitHub Copilot
+# generator README
 
-## Installation
+This is the README for your extension "generator". After writing up a brief description, we recommend including the following sections.
 
-### Quick Install (Pre-built)
+## Features
 
-1. Clone the repository:
-   
-   ```
-   bash :
+Describe specific features of your extension including screenshots of your extension in action. Image paths are relative to this README file.
 
-   git clone https://github.com/ishwaryaramesh200-byte/Generator-Agent.git
-   
-   cd Generator-Agent
-   
-   ```
+For example if there is an image subfolder under your extension project workspace:
 
-2. Reload VS Code:
-   
-   - Press `Ctrl+Shift+P`
-   - Type "Reload Window" and press Enter
+\!\[feature X\]\(images/feature-x.png\)
 
-## Usage
+> Tip: Many popular extensions utilize animations. This is an excellent way to show off your extension! We recommend short, focused animations that are easy to follow.
 
-1. Open GitHub Copilot Chat.
-2. Select the "Generators" agent.
-3. Start prompting.
+## Requirements
 
-## Features
+If you have any requirements or dependencies, add a section describing those and how to install and configure them.
+
+## Extension Settings
+
+Include if your extension adds any VS Code settings through the `contributes.configuration` extension point.
+
+For example:
+
+This extension contributes the following settings:
+
+* `myExtension.enable`: Enable/disable this extension.
+* `myExtension.thing`: Set to `blah` to do something.
+
+## Known Issues
+
+Calling out known issues can help limit users opening duplicate issues against your extension.
+
+## Release Notes
+
+Users appreciate release notes as you update your extension.
+
+### 1.0.0
+
+Initial release of ...
+
+### 1.0.1
+
+Fixed issue #.
+
+### 1.1.0
 
-- Static generator
-- Dynamic generator
-- Conditional generator
-- Reference generator
-- Remote generator
+Added features X, Y, and Z.
 
-## Instructions
+---
 
-### Getting Started
+## Working with Markdown
 
-| Step | Action | Details                                              |
-|------|--------|------------------------------------------------------|
-| 1    | Install| Follow the Quick Install steps                       |
-| 2    | Setup  | Copy `.github/agents` folder to your project root    |
-| 3    | Open   | Launch GitHub Copilot Chat in VS Code                |
-| 4    | Select | Choose "Generators" agent                            |
-| 5    | Prompt | Start using the agent with your requests             |
+You can author your README using Visual Studio Code.  Here are some useful editor keyboard shortcuts:
 
-### Key Commands
+* Split the editor (`Cmd+\` on macOS or `Ctrl+\` on Windows and Linux)
+* Toggle preview (`Shift+Cmd+V` on macOS or `Shift+Ctrl+V` on Windows and Linux)
+* Press `Ctrl+Space` (Windows, Linux, macOS) to see a list of Markdown snippets
 
-- **Start Agent**: `Ctrl+Shift+P` → "Start Generators Agent"
-- **Reload Window**: `Ctrl+Shift+P` → "Reload Window"
-- **Copilot Chat**: `Ctrl+Shift+I` (Open Copilot Chat panel)
+## For more information
 
-### Best Practices
+* [Visual Studio Code's Markdown Support](http://code.visualstudio.com/docs/languages/markdown)
+* [Markdown Syntax Reference](https://help.github.com/articles/markdown-basics/)
 
-1. Use the appropriate agent (Generators for configuration)
-2. Provide clear prompts for better generation results
-3. Test generated output before using in production
+**Enjoy!**

package/eslint.config.mjs

@@ -0,0 +1,25 @@
+import globals from "globals";
+
+export default [{
+    files: ["**/*.js"],
+    languageOptions: {
+        globals: {
+            ...globals.commonjs,
+            ...globals.node,
+            ...globals.mocha,
+        },
+
+        ecmaVersion: 2022,
+        sourceType: "module",
+    },
+
+    rules: {
+        "no-const-assign": "warn",
+        "no-this-before-super": "warn",
+        "no-undef": "warn",
+        "no-unreachable": "warn",
+        "no-unused-vars": "warn",
+        "constructor-super": "warn",
+        "valid-typeof": "warn",
+    },
+}];

package/extension.js

@@ -0,0 +1,36 @@
+// The module 'vscode' contains the VS Code extensibility API
+// Import the module and reference it with the alias vscode in your code below
+const vscode = require('vscode');
+
+// This method is called when your extension is activated
+// Your extension is activated the very first time the command is executed
+
+/**
+ * @param {vscode.ExtensionContext} context
+ */
+function activate(context) {
+
+	// Use the console to output diagnostic information (console.log) and errors (console.error)
+	// This line of code will only be executed once when your extension is activated
+	console.log('Congratulations, your extension "generator" is now active!');
+
+	// The command has been defined in the package.json file
+	// Now provide the implementation of the command with  registerCommand
+	// The commandId parameter must match the command field in package.json
+	const disposable = vscode.commands.registerCommand('generator.helloWorld', function () {
+		// The code you place here will be executed every time your command is executed
+
+		// Display a message box to the user
+		vscode.window.showInformationMessage('Hello World from Generator-Agent!');
+	});
+
+	context.subscriptions.push(disposable);
+}
+
+// This method is called when your extension is deactivated
+function deactivate() {}
+
+module.exports = {
+	activate,
+	deactivate
+}

package/jsconfig.json

@@ -0,0 +1,13 @@
+{
+	"compilerOptions": {
+		"module": "Node16",
+		"target": "ES2022",
+		"checkJs": true,  /* Typecheck .js files. */
+		"lib": [
+			"ES2022"
+		]
+	},
+	"exclude": [
+		"node_modules"
+	]
+}

package/package.json

@@ -1,63 +1,34 @@
 {
-    "name": "generator-agent",
-    "displayName": "GeneratorAgent",
-    "description": "A VS Code extension for conditional rule-based data generation",
-    "version": "1.0.7",
-    "publisher": "zohodesk",
-    "engines": {
-        "vscode": "^1.80.0"
-    },
-    "main": "./main.js",
-    "license": "MIT",
-    "homepage": "https://github.com/ishwaryaramesh200-byte/Generator-Agent",
-    "bugs": {
-        "url": "https://github.com/ishwaryaramesh200-byte/Generator-Agent/issues"
-    },
-    "scripts": {
-        "postinstall": "node post-install.js",
-        "setup": "node post-install.js"
-    },
-    "activationEvents": [
-        "onStartupFinished"
-    ],
-    "contributes": {
-        "commands": [
-            {
-                "command": "generator.start",
-                "title": "Start Generator Agent"
-            }
-        ],
-        "chatParticipants": [
-            {
-                "id": "generator",
-                "name": "GeneratorAgent",
-                "description": "Generator Agent responsible for generating generators",
-                "isSticky": true
-            }
-        ]
-    },
-    "repository": {
-        "type": "git",
-        "url": "https://github.com/ishwaryaramesh200-byte/Generator-Agent.git"
-    },
-    "categories": [
-        "Other"
-    ],
-    "keywords": [
-        "agent",
-        "generator",
-        "automation"
-    ],
-    "galleryBanner": {
-        "color": "#C80000",
-        "theme": "dark"
-    },
-    "devDependencies": {
-        "@types/vscode": "^1.80.0",
-        "@vscode/vsce": "^3.7.1"
-    },
-    "publishConfig": {
-        "access": "public",
-        "registry": "https://registry.npmjs.org/"
-    }
+  "name": "generator-agent",
+  "displayName": "Generator-Agent",
+  "description": "Create a generator for given use case",
+  "version": "1.0.8",
+  "engines": {
+    "vscode": "^1.109.0"
+  },
+  "categories": [
+    "Other"
+  ],
+  "activationEvents": [],
+  "main": "./extension.js",
+  "contributes": {
+    "commands": [{
+      "command": "generator.helloWorld",
+      "title": "Hello World"
+    }]
+  },
+  "scripts": {
+    "lint": "eslint .",
+    "pretest": "npm run lint",
+    "test": "vscode-test"
+  },
+  "publish": "npm publish --access public",
+  "devDependencies": {
+    "@types/vscode": "^1.109.0",
+    "@types/mocha": "^10.0.10",
+    "@types/node": "22.x",
+    "eslint": "^9.39.2",
+    "@vscode/test-cli": "^0.0.12",
+    "@vscode/test-electron": "^2.5.2"
+  }
 }

package/test/extension.test.js

@@ -0,0 +1,15 @@
+const assert = require('assert');
+
+// You can import and use all API from the 'vscode' module
+// as well as import your extension to test it
+const vscode = require('vscode');
+// const myExtension = require('../extension');
+
+suite('Extension Test Suite', () => {
+	vscode.window.showInformationMessage('Start all tests.');
+
+	test('Sample test', () => {
+		assert.strictEqual(-1, [1, 2, 3].indexOf(5));
+		assert.strictEqual(-1, [1, 2, 3].indexOf(0));
+	});
+});

package/vsc-extension-quickstart.md

@@ -0,0 +1,42 @@
+# Welcome to your VS Code Extension
+
+## What's in the folder
+
+* This folder contains all of the files necessary for your extension.
+* `package.json` - this is the manifest file in which you declare your extension and command.
+  * The sample plugin registers a command and defines its title and command name. With this information VS Code can show the command in the command palette. It doesn’t yet need to load the plugin.
+* `extension.js` - this is the main file where you will provide the implementation of your command.
+  * The file exports one function, `activate`, which is called the very first time your extension is activated (in this case by executing the command). Inside the `activate` function we call `registerCommand`.
+  * We pass the function containing the implementation of the command as the second parameter to `registerCommand`.
+
+## Get up and running straight away
+
+* Press `F5` to open a new window with your extension loaded.
+* Run your command from the command palette by pressing (`Ctrl+Shift+P` or `Cmd+Shift+P` on Mac) and typing `Hello World`.
+* Set breakpoints in your code inside `extension.js` to debug your extension.
+* Find output from your extension in the debug console.
+
+## Make changes
+
+* You can relaunch the extension from the debug toolbar after changing code in `extension.js`.
+* You can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with your extension to load your changes.
+
+## Explore the API
+
+* You can open the full set of our API when you open the file `node_modules/@types/vscode/index.d.ts`.
+
+## Run tests
+
+* Install the [Extension Test Runner](https://marketplace.visualstudio.com/items?itemName=ms-vscode.extension-test-runner)
+* Open the Testing view from the activity bar and click the Run Test" button, or use the hotkey `Ctrl/Cmd + ; A`
+* See the output of the test result in the Test Results view.
+* Make changes to `test/extension.test.js` or create new test files inside the `test` folder.
+  * The provided test runner will only consider files matching the name pattern `**.test.js`.
+  * You can create folders inside the `test` folder to structure your tests any way you want.
+
+## Go further
+
+ * [Follow UX guidelines](https://code.visualstudio.com/api/ux-guidelines/overview) to create extensions that seamlessly integrate with VS Code's native interface and patterns.
+ * [Publish your extension](https://code.visualstudio.com/api/working-with-extensions/publishing-extension) on the VS Code extension marketplace.
+ * Automate builds by setting up [Continuous Integration](https://code.visualstudio.com/api/working-with-extensions/continuous-integration).
+ * Integrate to the [report issue](https://code.visualstudio.com/api/get-started/wrapping-up#issue-reporting) flow to get issue and feature requests reported by users.

package/.agents/generators.json

@@ -1,7 +0,0 @@
-{
-    "id": "generator",
-    "name": "GeneratorAgent",
-    "description": "Generator Agent responsible for generating generators",
-    "scope": "folder",
-    "folderScoped": true
-}

package/.agents/generators.md

@@ -1,19 +0,0 @@
-# Generators
-
-You are a Generator Configuration Agent responsible for creating data generators based on specifications.
-
-## Instructions
-
-1. Read and understand generator patterns and type definitions
-2. Create generators based on schemas and dependencies
-3. Ensure all references are valid
-4. Follow naming conventions
-5. Use the correct generator type
-
-## Capabilities
-
-- Static generator creation
-- Dynamic generator creation
-- Conditional generator creation
-- Reference generator creation
-- Remote generator creation

package/.github/agents/Generators.agent.md

@@ -1,121 +0,0 @@
----
-name: GeneratorAgent
-description: Creates generators using the OpenAPI specification and defined generator patterns. Ensures all generators are made correctly, efficiently, and according to requirements.
----
-
-## Role
-Responsible for building generators that follow strict rules and guidelines based on OpenAPI and specified patterns.
-
----
-
-## What to do
-
-1. Read all generator type definitions in the Generator_Patterns folder to understand their rules and structures, then use them to create generators based on the OAS file’s schema and dependencies.
-
-2. Analyze the user prompt to identify only the dependencies explicitly requested by the user. Do not add extra setup dependencies on your own.
-
-3. For user-requested dependencies, ensure generators extract the required values from API responses so downstream generators can consume them clearly and correctly.
-
-4. Always create a new generator file instead of modifying existing ones. If you need to modify or add to an existing generator, request explicit user permission before proceeding.
-
-5. Refer to the `PathConfig.properties` file to find the paths for OAS files and existing generator files. Always use these paths when reading or referencing OAS or generator files.
-
-6. Use only the dependencies explicitly provided in the user prompt. Do not include every parameter listed in the OAS, and do not auto-create additional dependency generators unless the user explicitly asks.
-
-7.  Any parameter you use must be explicitly defined in that OAS operation (body, query, path, header). Never invent fields, wrapper keys, or placeholders. Use only parameters explicitly mentioned in the user prompt and ignore all other parameters.
-
-8. You may use tools if necessary to generate the generators correctly.
----
-
-## Generator
-
-1. Generator names must use snake_case (all lowercase, underscores), be clear, consistent, and meaningful, matching the resource and purpose. Use singular for single values (e.g., entity_id), plural for lists (e.g., entity_ids). All generator names must be unique and kept short and meaningful.
-
-2. Maintain order in generator creation based on dependencies. If Generator A depends on Generator B, ensure that Generator B is created before Generator A.
-
-3. Ensure that all generators strictly follow the definitions and rules specified in the generator type definition files.
-
-4. Choose the correct generator type strictly according to its definition file.
-
-5. For the "name" field inside a generator, use the resource name from PathConfig in snake_case: plural for lists, singular for single items (e.g., "resources", "resource", "records").
-
-6. Follow exact reference syntax, dataPath format, and structural rules as defined in the type definition files and README.md.
-
-7.  Output must contain only the "generators" JSON object.
-
-8.  When using short-hand references like `$departments` or `$contacts`, ensure they reference generators defined in the same `test_data_generation_configurations.json` file unless the reference explicitly uses a relative cross-file path (for example `../Department/...`). This prevents accidental cross-file name collisions and keeps generated params local by default.
-
-9. Operation ID format: Always specify `generatorOperationId` using the `<service>.<Entity>.<operation>` pattern (for example: "generatorOperationId": "support.Agent.getAgents").
-
-10. When params are used in a dynamic generator, the parameter names should be the same as those defined in the OpenAPI specification.
-
-11. If you use param input from body, query, path or header, please make sure the reference path is correct and the field exists in the OpenAPI specification. For example: "$.input.body:$.ticketId" for request body, "$.input.query:$.status" for query parameter, "$.input.path:$.agentId" for path parameter, "$.input.header:$.Authorization" for header.
-
-12. If the same API with the same payload is needed more than once, call that API only once, store the entire response object, and extract all required values from that stored response.
-
-13. When storing an entire object in a generator, the `dataPath` must use the `:$` format (for example: `$.response.body:$`).
-
----
-
-## Generator Structure Rule
-
-All generators must be created using the following structure:
-
-```json
-{
-    "generators": {
-        "<generator_name>": [
-        {}
-        ]
-    }
-}
-```
-
-- All dependencies for a generator must be included in the same array under the generator name.
-- This ensures clarity, maintainability, and proper grouping of related generator steps.
-- Generator name should be descriptive of the entity and purpose, following the snake_case convention.
----
-
-## Generator Creation Rules
-
-1. Create subfolder with PascalCase name (e.g., `CreateContact`, `CreateTicket`) in `Created_Generators` directory, add `test_data_generation_configurations.json` inside.
-
-2. Only create the generator JSON file.
-
-3. Always create new generator files instead of modifying existing ones. Request explicit permission before editing existing generators.
-
----
-
-## Prompt Handling Rules
-
-1. **Direct Prompt**: When user provides a direct prompt (e.g., "Create Contact", "Create Ticket"), implement the generator immediately without preamble like "Create generator for X".
-
-2. **Explicit Request**: When user explicitly says "Create a generator for X" or similar, proceed as normal with full context.
-
-3. **Skip Explanation**: For direct prompts, go straight to building the generator, no explanations.
-
-4. **Clarify Ambiguity First**: If there is any confusion about which generator to use, which data to extract, or how required values should be sourced, ask the user first and generate only after confirmation.
-
-5. **No Implicit Body Defaults**: For implied actions (for example, "add comments"), do not auto-fill request body fields that were not provided in the prompt. Ask the user for missing values first.
-
-6. **Optional Param Choice**: In ambiguous enum/choice situations, ask the user with available options and include one extra option: **"Don't consider this param"**. If the user selects it, omit that parameter from the generator.
-
----
-
-## Do Not:
-
-1. Don't Invent new generator types or modify existing rules.
-
-2. Don't modify or generate any section other than "generators" in the test_data_generation_configurations.json file.
-
-3. Don't include explanations, comments, markdown, or extra text in the final output.
-
-4. Don't edit OpenAPI specification files.
-
-5. Never include any param or field in a generator unless it is explicitly defined in the OAS for that operation.
-
-6. Don't auto-add setup generators (for example Contact/Department/Account) unless those dependencies are explicitly requested by the user.
-
-7. Don't ask permission for read access to OAS or generator files, as you have full access to read any file in the specified paths.You have permission to read files outside of the workspace.
-
-8. Don't give text response in chat window.Only output the generator JSON object as specified.

package/.vscode/agents.json

@@ -1,11 +0,0 @@
-{
-  "agents": [
-    {
-      "id": "generator",
-      "name": "GeneratorAgent",
-      "description": "Generator Agent responsible for generating generators"
-    }
-  ],
-  "registeredAt": "2026-02-26T07:34:16.245Z",
-  "installedFrom": "/home/ish-zstk410/Agent"
-}

package/.vscode/settings.json

@@ -1,6 +0,0 @@
-{
-  "github.copilot.chat.experimental.agents": true,
-  "github.copilot.chat.experimental.agentLocations": [
-    ".vscode/agents.json"
-  ]
-}

package/Generator_Patterns/Conditional.md

@@ -1,84 +0,0 @@
-# CONDITIONAL Generator — Rule-Based Data Selection
-
----
-
-## Overview
-
-A **Conditional Generator** selects a data generator based on predefined conditions. It enables dynamic test data generation by evaluating input values or context and branching to different generator logic accordingly.
-
----
-
-## When to Use
-
-- When the value of a parameter depends on other input values or request context.
-- To implement business rules, feature flags, or scenario-specific data.
-- For fallback/default logic when no condition matches.
-
----
-
-## Structure
-
-A conditional generator contains:
-- `type`: Must be `"conditional"`
-- `conditions`: List of condition objects, each with:
-	- `when`: The condition to evaluate (key, operator, value)
-	- `then`: The generator or value to use if the condition matches
-- `else`: (optional) The generator or value to use if no conditions match
-
----
-
-## Example
-
-```json
-{
-	"generators": {
-		"snippet_id": [
-			{
-				"type": "conditional",
-				"conditions": [
-					{
-						"when": {
-							"key": "$.input.query:modules",
-							"equals": "tickets"
-						},
-						"then": {
-							"use": "$generators:#/generators/ticket_id"
-						}
-					},
-					{
-						"when": {
-							"key": "$.input.query:modules",
-							"equals": "contacts"
-						},
-						"then": {
-							"use": "$generators:#/generators/contact_id"
-						}
-					}
-				],
-				"else": "$generators:#/generators/activity_id"
-			}
-		]
-	}
-}
-```
-
----
-
-## Best Practices
-
-- Use input-based branching: reference request path, query, or body fields in `when`.
-- Reference other generators in `then` using correct relative paths or `$generators:` syntax.
-- Always provide an `else` clause if possible to avoid unexpected nulls.
-- Keep conditions mutually exclusive and clear.
-- Avoid deeply nested or overly complex chains for readability.
-
----
-
-## Validation Checklist
-
-- Ensure all referenced generators exist.
-- Test each condition path for expected output.
-
----
-
-*Last Updated: 17 February 2026*