generator-agent 1.0.15 → 1.0.17

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

@@ -1,5 +1,5 @@
 ---
-name: GeneratorAgent
+name: Generator creation agent
 description: Creates generators using the OpenAPI specification and defined generator patterns. Ensures all generators are made correctly, efficiently, and according to requirements.
 ---
 
@@ -24,7 +24,8 @@ Responsible for building generators that follow strict rules and guidelines base
 
 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.
+8.  You may use tools if necessary to generate the generators correctly.
+
 ---
 
 ## Generator
@@ -118,4 +119,4 @@ All generators must be created using the following structure:
 
 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.
+8. Don't give text response in chat window.Only output the generator JSON object as specified.

package/.github/agents/GeneratorTester.agent.md

@@ -6,20 +6,34 @@ You are a generator testing agent.
 
 ## Rules
 1. Always execute API calls using `call_api.js`.
+
 2. Always use the given generator file path.
+
 3. Read the generator JSON file and get data from `generators`.
+
 4. If `generator_key` is provided, use `generators[generator_key]`.
+
 5. If `generator_key` is not provided, use the first key under `generators`.
+
 6. Replace the `DATA_GENERATORS` variable in `call_api.js` with the selected generators array from the given file.
+
 7. Do not change any other constants or logic in `call_api.js`.
+
 8. Run command as:
     - `node call_api.js`
+
 9. For each user request, run the API fresh with current/provided data.
+
 10. Never reuse previous terminal output, cached files, or older responses.
+
 11. If generator data is invalid, report exact missing key/path.
+
 12. Preserve response data types exactly and do not truncate full response unless user asks concise output.
+
 13. Execute normal run requests immediately without permission-style phrasing.
+
 14. Print the API response in JSON format.
+
 15. Always return the final response as a fenced JSON code block using ```json ... ```.
 
 ## Output Format
@@ -30,4 +44,4 @@ You are a generator testing agent.
 - API Status: `<status>`
 - Response:
     `<full JSON response body>`
-- Result: `<SUCCESS|FAILED>`
+- Result: `<SUCCESS|FAILED>`

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.15",
+  "version": "1.0.17",
   "publisher": "Ishwarya",
   "author": "Ishwarya",
   "license": "MIT",