generator-agent 1.0.23 → 1.0.25

package/.github/agents/Generator.agent.md

@@ -1,5 +1,5 @@
 ---
-name: Generator-agent
+name: Generator Agent 
 description: Creates generators using the OpenAPI specification and defined generator patterns. Ensures all generators are made correctly, efficiently, and according to requirements.
 ---
 
@@ -12,20 +12,15 @@ Responsible for building generators that follow strict rules and guidelines base
 
 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.
+2. **Strict Rule (Non-Negotiable):** Add only dependencies, fields, and parameters explicitly mentioned by the user. Do not guess from old generators, past outputs, OAS specs, or optional fields. Do not auto-create additional dependency generators unless explicitly asked.
 
 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.
+4. 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.
 
-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.
+6. You may use tools if necessary to generate the generators correctly.
 
+7. **Strict Rule (Non-Negotiable):** Follow all agent rules for every request and response without exception. Validate output against these rules before finalizing, and do not skip any rule.
 ---
 
 ## Generator
@@ -34,11 +29,9 @@ Responsible for building generators that follow strict rules and guidelines base
 
 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.
+3. Choose the correct generator type and ensure 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").
+4. For the `name` field inside a generator, use snake_case and keep it resource-specific and meaningful. Use singular for single values (for example: `ticket_id`) and plural for lists (for example: `ticket_ids`).
 
 6. Follow exact reference syntax, dataPath format, and structural rules as defined in the type definition files and README.md.
 
@@ -50,12 +43,18 @@ Responsible for building generators that follow strict rules and guidelines base
 
 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.
+11. If you use param input from body, query, path, or header, make sure the input 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:$`).
 
+14. Do not hardcode business values (for example department names/ids, status values, or entity identifiers) when they can be provided at runtime. Prefer parameterized input references (for example `$.input.query`, `$.input.body`, `$.input.path`, `$.input.header`) and pass them through generator params.
+
+15. When a runtime value is expected directly in `params`, provide it as an explicit placeholder string in this format: `"<provide_param_name>"` (for example: `"searchStr": "<provide_department_name>"`). Do not hardcode concrete business values.
+
+15. The first generator in any generator list must not be of type `reference`. Start with a data-producing generator type (for example `dynamic`, `static`, `remote`, or `conditional`) and use `reference` only after an earlier step has produced source data.
+
 ---
 
 ## Generator Structure Rule
@@ -79,7 +78,7 @@ All generators must be created using the following structure:
 
 ## Generator Creation Rules
 
-1. Create subfolder with PascalCase name (e.g., `CreateContact`, `CreateTicket`) in `Created_Generators` directory, add `test_data_generation_configurations.json` inside.
+1. Read `PathConfig.properties` to get the `CREATED_GENERATOR_PATH` directory path, then create a subfolder with PascalCase name (e.g., `CreateContact`, `CreateTicket`) inside it, and add `test_data_generation_configurations.json` inside the subfolder.
 
 2. Only create the generator JSON file.
 
@@ -101,6 +100,8 @@ All generators must be created using the following structure:
 
 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:
@@ -116,7 +117,3 @@ All generators must be created using the following structure:
 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/README.md

@@ -1,6 +1,4 @@
-# AgentPublishTest - VS Code Extension
-
-A powerful VS Code extension that integrates custom AI agents with multiple UI interfaces - dropdown selection, chat panel, and command palette.
+# generator-agent - VS Code Extension
 
 ## Features
 
@@ -16,16 +14,12 @@ A powerful VS Code extension that integrates custom AI agents with multiple UI i
 
 #### To install the latest version, run:
 
-```bash
-npm install generator-agent@latest
-npx generatoragent init
+# Step1: Install the extension from npm package:
+- npm install generator-agent@latest
 
-**Agents not appearing in dropdown?**
-- Make sure agents are in `.github/agents/` folder
-- Check file extension is `.agent.md`
-- Reload VS Code window after adding agents
+# Step2 : Run the initialization command to set up the extension:
+- npx generatoragent init
 
-### Supported
+# Step3: Reload VS Code window to activate the extension.
+- Reload VS Code window after adding agents
 
-For issues and feature requests, visit:  
-[GitHub Issues](https://github.com/ishwaryaramesh200-byte/AgentPublishTest/issues)

package/package.json

@@ -2,7 +2,7 @@
   "name": "generator-agent",
   "displayName": "GeneratorAgent",
   "description": "Custom agent that responds with greetings and follows specific instructions",
-  "version": "1.0.23",
+  "version": "1.0.25",
   "publisher": "Ishwarya",
   "author": "Ishwarya",
   "license": "MIT",
@@ -18,7 +18,7 @@
   ],
   "repository": {
     "type": "git",
-    "url": "https://github.com/ishwaryaramesh200-byte/AgentPublishTest.git"
+    "url": "https://zrepository.zohocorpcloud.in/zohocorp/user/IshwaryaRamesh_26/Test_Data_Generation.git"
   },
   "keywords": [
     "agent",
@@ -28,9 +28,9 @@
     "ai",
     "automation"
   ],
-  "homepage": "https://github.com/ishwaryaramesh200-byte/AgentPublishTest#readme",
+  "homepage": "https://zrepository.zohocorpcloud.in/zohocorp/user/IshwaryaRamesh_26/Test_Data_Generation#readme",
   "bugs": {
-    "url": "https://github.com/ishwaryaramesh200-byte/AgentPublishTest/issues"
+    "url": "https://zrepository.zohocorpcloud.in/zohocorp/user/IshwaryaRamesh_26/Test_Data_Generation.git"
   },
   "engines": {
     "vscode": "^1.109.0"
@@ -39,11 +39,6 @@
     "Other",
     "AI"
   ],
-  "activationEvents": [
-    "onCommand:my-agent.selectAgent",
-    "onCommand:my-agent.openChatPanel",
-    "onCommand:my-agent.runFromPalette"
-  ],
   "main": "./extension.js",
   "contributes": {
     "commands": [